“ITMS-90338”

For the past month, I've been trying to upload several binaries to no avail. See below error message below. From my understanding of others that have faced this issue, all points to a validation error by Apple. Anyone can help me resolve this issue? Dear Developer, We identified one or more issues with a recent delivery for your app, {{app_name}} 5.0.0 (6). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in Opencash: _isKeyDown, _modifiedInput, _modifierFlags, isPassthrough, onSuccess:, removeValuesForKeys:completion:. 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://develop

I use this package in my app: https://github.com/liamnichols/_InternalSwiftSyntaxParser which contains an xcframework: _InternalSwiftSyntaxParser.xcframework which contains dylib files All is good with this package, my app works well in simulator and real device. But when I uploaded a version to the App Store Connect, I got this error message: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Is there a solution for that? I searched a lot with out any chance to solve it. What I tried: (1) I tried to add manually the SwiftSupport folder using the script here: https://gist.github.com/adamzarn/6bb89d91ed4b8c3d3fb25363c221441f (2) Then the error message is now: ITMS-90430: Invalid Swift Support - The file lib_InternalSwiftSyntaxParser.dylib doesn’t have a signing ID. Sign the file, rebuild your app using the current public (GM) version of Xcode, and resubmit it. (3) Trying to signing the file u

I use the promotion function (https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/promoting_in-app_purchases)) within the app. It worked well up to the iOS15 environment, but during the iOS16 beta test, it was confirmed that it did not work properly. When tested according to the guide (https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/testing_promoted_in-app_purchases)), iOS15 calls paymentQueue:shouldAddStorePayment:delegate normally, but iOS16 does not call paymentQueue:shouldAddStorePayment:. The link used for the test is itms-services://?action=purchaseIntent&bundleId=com.nhn.cloud.client.sdk&productIdentifier=com.nn.cloud.iap.gem99 Is there a problem with iOS16?

Backend is automatically refusing app uploads to app store connect. In the refusal email no API is mentioned which is being used. Dear Developer, We identified one or more issues with a recent delivery for your app, Perma Evidence Pro 1.0 (1). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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

When I uploaded build on TestFlight its processing and then rejected because of following response ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/