Question 130627 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode – ITMS-90338: Non-public API usage PROCESSING ERROR – Previously Working

Upon uploading a binary to App Store Connect, I receive this email from Apple:

ITMS-90338: Non-public API usage – The app references non-public selectors in [PROJECT NAME HERE]: callWithArguments:, estimatedProgress, frameInfo, getVersion, initWithFrame:configuration:, isMainFrame, navigationDelegate, navigationType, setNavigationDelegate:, setProcessPool:, targetFrame, toDouble, toString, userContentController. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

However, other than the build number increasing from 1.2 to 1.2.1, this is the exact same Binary that has been previously uploaded (and is live).

I’ve checked other questions on StackOverflow, such as this and this, however are typically in reference to third party SDKs.

I am completely baffled as I don’t use these method names at all, anywhere in the project…

Is this an issue with iOS 16 having been just released?
Thank you.

Tags:

2

Answers


  1. 0

    UPDATE
    This issue has been resolved on the app validation backend. Resubmitting should work.
    source

    Original Answer

    I’m also experiencing this issue this morning. A simple search of my project reveals many usages of these WKWebView APIs that are clearly public.

    I suspect the issue is due to an issue with App Store builds linking against the freshly announced iOS16/Mac updates this morning. Unless those APIs have been outright banned today with no warning (unlikely), I’d put money on it being an Apple issue which they will resolve ASAP.

    Login or Signup to reply.
  2. 0

    I tried many ways online but finally found one way out. Refer to this comment on the gihub issue. Hope you find this helpful!

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search