ITMS-90338: Non-public API usage automatic refuse

Hello,


We contacted Apple Developer Support due to an automatic message we receive when trying to publish a new version of our app



Dear Developer,
We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again. 
ITMS-90338: Non-public API usage - The app references non-public selectors in Idealys: applicationWillTerminate,
 ddSetLogLevel:, localTarget, newSocketQueueForConnectionFromAddress:onSocket:, setOrientation:animated:,
 socket:didConnectToHost:port:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:,
 socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, 
socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidSecure:,
 terminateWithSuccess, webSocket:didReceiveMessage:, webSocketDidOpen:

 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/ 

Best regards,

The App Store Team


The problem is we do not understand what the issue is even when reading your automatic message.


How can we debug this ?

How can we identify the source of the problem ?

Do you have any idea of what the problem is ?


What we tried :

  1. We tried to re-publish the application we currently have on your store (production) with different build number => App rejected with the same automatic message ;
  2. We tried to disable one by one every cordova plugin (see the list below) => App rejected with the same automatic message ;
  3. We tried to look for every reference listed in the automatic message using XCode and grep => We found none of those ;
  4. We tried to upgrade cordova-ios => App rejected with the same automatic message ;


XCode version : 11.0

MacOS version : 10.14.6

Cordova-ios version : 4.5.5

Ionic version : 1


Best regards,

Post not yet marked as solved Up vote post of hector.glez4 Down vote post of hector.glez4
66k views
Posted by
hector.glez4
Reply

  • Same to me... ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/Capacitor.framework/Capacitor: applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, targetFrame.

    —
    NBulla

  • I'm also seeing this issue as of today without adding any new packages.

    —
    devmop

  • ITMS-90338: Non-public API usage - The app references non-public selectors in NNNN estimatedProgress, initWithFrame:configuration:, initWithURL:configuration:, initWithURL:entersReaderIfAvailable:, isMainFrame, ...etc

    Found this https://news.ycombinator.com/item?id=31648690 I think someone introduced a lookup issue in apples code validator.

    Let's hope this is resolved pronto. Well at least Android is working (that was a passive aggressive dig).;

    —
    dandoyon

Apple Recommended

The issue has been resolved on the app validation backend. Please try resubmitting. Sorry for the trouble.

Posted by
App Store Connect Engineer
Post not yet marked as solved Up vote reply of App Store Connect Engineer Down vote reply of App Store Connect Engineer
Post marked as Apple Recommended

  • Thanks a lot. ^^

    —
    myeong yong shin

  • it worked, thanks!

    —
    bmitioglov

  • Thanks for the fix. I just uploaded a new build and it works!

    —
    konekoya

Replies

Same here. I even tried with a git reset head to make sure it was exactly the same version. I'm using the latest version of capacitor, nothing else.

ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/Capacitor.framework/Capacitor: applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, targetFrame.

Posted by
jcardeira
Post not yet marked as solved Up vote reply of jcardeira Down vote reply of jcardeira
Add a Comment

I'm also experiencing this issue this morning. A simple search of my project reveals many uses 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.

Posted by
jeremysom
Post not yet marked as solved Up vote reply of jeremysom Down vote reply of jeremysom
Add a Comment

Sadly, we go through this every once in a while when a silly bug is introduced into the private API string compare list. My team is now blocked as well and it's not a good time for such a bug. Usually, this gets worked out by someone filing a RADAR. Given the blast radius, I'm assuming this has already been filed and hoping for a quick resolution. The longest I've seen was in 2020 for 10 days though.

Posted by
ubnt-ethan
Post not yet marked as solved Up vote reply of ubnt-ethan Down vote reply of ubnt-ethan
Add a Comment

I have the same problem with a project that was successfully built and published a couple of days ago. I know my comment does not help but just wanted to pitch it to get visibility that this issue is affecting many projects.

My project is on React Native and the new build that is failing is only a few lines different (and Javascript lines, not even native iOS). No new or upgraded dependences.

If it helps, there is this issue in the React Native project: https://github.com/facebook/react-native/issues/33789 It seems that the problem is not with a specific framework but with Apple, but that thread became quite active today so any news there might help.

Posted by
diegodev
Post not yet marked as solved Up vote reply of diegodev Down vote reply of diegodev
Add a Comment

Having this problem with instabug. Please fix apple that I need to do hotfixes

Posted by
experiment626
Post not yet marked as solved Up vote reply of experiment626 Down vote reply of experiment626
Add a Comment

Same problem here. I was pushing app updates (small incremental changes) to testflight. I didn't do any change in packages. I was pushing OK until some time today.

The exact wording of the error message:

The app references non-public selectors in Payload/App.app/Frameworks/Capacitor.framework/Capacitor: __swift_objectForKeyedSubscript:, applicationNameForUserAgent, initWithFrame:configuration:, isMainFrame, setNavigationDelegate:, targetFrame With error code STATE_ERROR.VALIDATION_ERROR.50 for id 24e410ba-55a9-443c-bc9a-0e20ae7f76b2

Also the app validates just fine.

Posted by
therist
Post not yet marked as solved Up vote reply of therist Down vote reply of therist
Add a Comment

Hi, I got an email with this exact error, but my build is showing on App Store connect as ready to publish, all looks fine. Maybe they've just fixed this issue?

Posted by
Smiffter
Post not yet marked as solved Up vote reply of Smiffter Down vote reply of Smiffter
Add a Comment

same here, this didn't start for us until today - no library/pod changes and all of the sudden apple is complaining about methods/selectors that are being used by pods we've used for years and successfully submitted app review

ITMS-90338: Non-public API usage - The app references non-public selectors in XXXXXXX: estimatedProgress, initWithFrame:configuration:, isMainFrame, navigationType, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, setNavigationDelegate:, setProcessPool:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, targetFrame, userContentController, websiteDataStore. 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/

Posted by
h3knix
Post not yet marked as solved Up vote reply of h3knix Down vote reply of h3knix
Add a Comment

Same here... I uploaded a build to testFlight on Friday, but today i get this error too when build my app using cross-platform framework Titanium.

The app references non-public selectors in Payload/Caixa Previdência.app/Caixa Previdência: callWithArguments:, dataChanged, estimatedProgress, frameInfo, initWithFrame:configuration:, initWithURL:configuration:, initWithURL:entersReaderIfAvailable:, initialURL, isMainFrame, isNumber, isObject, matchFound, navigationType, setException:, setNavigationDelegate:, setProcessPool:, targetFrame, toArray, toDictionary, toObject, userContentController, websiteDataStore With error code STATE_ERROR.VALIDATION_ERROR.50 for id ...

Posted by
jordanbisato
Up vote reply of jordanbisato Down vote reply of jordanbisato
Add a Comment

Having the same issue with react 0.65.1 with one of my apps and the other (same rn version) is not experiencing issue. It's also happening after minor updates (only chaging litterally one character and the version number)

Posted by
Bantotal
Post not yet marked as solved Up vote reply of Bantotal Down vote reply of Bantotal
Add a Comment

We started having the same issue today.

Adding my specific error message here, which seems to be duplicated above, so that hopefully we are notified once the issue has been resolved:

ITMS-90338: Non-public API usage - The app references non-public selectors in ibble: __swift_objectForKeyedSubscript:, authorizedScopes, createRequest, estimatedProgress, isMainFrame, isPassthrough, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, relativeSize, removeValuesForKeys:completion:, setNavigationDelegate:, setProcessPool:, setRequestedOperation:, setRequestedScopes:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, spanArray, spanArray_Count, toggleEditing:, underline, userContentController, websiteDataStore. 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/

Like many we were good w/ a build and minutes later w/ no change other than meta-data things started to fail.

Posted by
jzaleski
Up vote reply of jzaleski Down vote reply of jzaleski
Add a Comment

Same here after just a version bump.

Posted by
tedik
Up vote reply of tedik Down vote reply of tedik
Add a Comment

Having a similar issue here. I last updated my Unity app less than one month ago, I've made very few changes to my code in that time.

Here's my error:

ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/UnityFramework.framework/UnityFramework: applicationWillFinishLaunchingWithOptions:, callWithArguments:, didReceiveRemoteNotification:, estimatedProgress, frameInfo, initWithFrame:configuration:, isMainFrame, loadPlugin, navigationType, setNavigationDelegate:, setProcessPool:, toDouble, toString, userContentController.

Seems like I'm not alone, hopefully Apple is on this...

Thanks.

Posted by
9 Cent Games
Up vote reply of 9 Cent Games Down vote reply of 9 Cent Games
Add a Comment

Also experiencing this issue as of today without any changes to my build process or code

Posted by
kmatherne
Up vote reply of kmatherne Down vote reply of kmatherne
Add a Comment

Same problem. It seems to be something related to Apple itself.

Posted by
saulo_ferreira
Up vote reply of saulo_ferreira Down vote reply of saulo_ferreira
Add a Comment