Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

Not working Testing Promoted In-App Purchases in iOS16
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?
1
0
805
Aug ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
We are facing similar issue.. The app we are trying to upload is a sample camera app from Apple only. AVMulticamPIP sample. In the refusal email even though it says non-public API usage, no API names are mentioned for which it is refusing. This is the email we got 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 Stor
Jul ’22
ITMS-90338: Non-public API usage
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
0
0
418
Jul ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same here, 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/ -xcode version: 13.2.1 (Latest Compatible Unity Cloud Build) -unity version: 2020.3.32f1
Jul ’22
ITMS-90338: Non-public API usage
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/
0
0
430
Jul ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same here, 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/ macOS 11.6 xcode 13.0
Jul ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same problem. I have uploaded some days ago, but, today, I can't send a new build of my app. 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/ Xcode 13.4.1 Mac 12.4 M1 Native app with ObjC and Swift classes.
Jul ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
Same issue with WebRTC library (using for our framework) ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/CallCenter.framework/CallCenter: connectionState, sdp, setIsAudioEnabled:, trackId,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/
Jul ’22
Reply to can't upload test flight app store connect
Hey! Did you manage to upload since you posted? I experience the same issue with some other issues, when I manage to upload from xCode, I get later an email saying ITMS-90338: Non-public API usage, but after a through investigation, I couldn't find anything wrong. Also when I tried to re-upload the same code that is already in stores with a different version number got the same problem. Created a ticket for apple but no way to escalate or get a quick response yet.
Jul ’22
Reply to ITMS-90338: Non-public API usage automatic refuse
I'm having the same issue with HMS SDK Framework in React Native: ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/HMSSDK.framework/HMSSDK: cropHeight, cropWidth, cropX, cropY, dataU, dataV, dataY, initWithBuffer:rotation:timeStampNs:, initWithURLStrings:, maxBitrateBps, newI420VideoFrame, sendData:, setCategoryOptions:, setInputImage:, setIsActive:, setIsAudioEnabled:, setIsEnabled:, setMaskImage:, setMaxBitrateBps:, setMaxFramerate:, setNetworkPriority:, setRid:, setScaleResolutionDownBy:, setStreamIds:, strideU, strideV, strideY, timeStampNs, toI420, videoSource,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
Jul ’22
Reply to State_error.validation_error.10
Interestingly, I was getting the validation 10 error until I updated my system to the latest macOS version. Only then did i start getting this error via email; ITMS-90338: Non-public API usage Theres been basically no changes to this app since the last successful upload, so I don't really know what it could be referring to.
Jul ’22
ITMS-90338 Non-Public API Usage
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 !!! Please tell us how to solve this problem step by step !!!
2
0
1.3k
Jul ’22
Reply to State_error.validation_error.10
Getting the same Issue:- The app contains one or more corrupted binaries. Rebuild the app and resubmit. With error code STATE_ERROR.VALIDATION_ERROR.10 for id xxxxx And sometimes If the build gets uploaded to appstoreconnect, a failure mail is there in few minutes 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/ Did someone got the solution?
Jul ’22