ITMS-90338

1,572 results found

Post

Replies

Boosts

Views

Activity

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/ There weren't any third party SDK or Unity updates since the last version. And the last version(20220723) is OK, how can I identify the source of the problem? I'm using Unity 2019.4.17f1c1 with MacOS 12.4 and XCode 13.4.1.
2
0
760
Jul ’22
ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries.
After deploying my (ReactNative) app on testflight, I receive an email saying: Dear Developer, We identified one or more issues with a recent delivery for your app, [AppName]. 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. [...] Best regards, The App Store Team Has someone more information about this?
3
0
1.7k
Jul ’22
"ITMS-90338: Non-public API usage" Build issue
When I try to submit my app build I get this error. I have no idea which API it is clashing with. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app references non-public selectors in Frameworks/react_native_webrtc.framework/react_native_webrtc: addStream:, initWithBuffer:rotation:timeStampNs:, initWithURLStrings:, isBinary, localDescription, sdp, sendData:, setChannelId:, setIsEnabled:, stringForType:, typeForString:, videoSource. 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/
1
0
1.1k
Jul ’22
How can i solve this problem with iOS game upload?
I´m getting an error all the time when uploading an update for my latest iOS game, yesterday I uploaded the 1st version and everything went good, but today I´m trying to update it and I´m getting all the time this: 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/ I tried multiple things and nothing worked... I saw lots of blogs and videos and nothing... Can anyone help me?
1
0
1.6k
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
Reply to ITMS-90338: Non-public API usage automatic refuse
So today the same issue for me, however not that specific as you guys have: 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.
Jul ’22
MainWindow~ipad.nib not found????
I recently updated our app's info.plist to address a black screen on startup issue with the iPod touch. In my info.plist I changed the key from Main nib file base name (iPhone) to Main nib file base name, which fixed the issue with the black screen and now when I try to submit to iTunesConnect I get the error below.ERROR ITMS-90030: “Nib file ‘MainWindow~ipad.nib’ was not found. Please ensure the specified file is included in the bundle with any required device modifiers appended to the filename.”Can anyone explain why this is happening?
4
0
2.0k
Dec ’15
ITMS-90286: Invalid Code Signing Entitlements but the application-identifier is exactly what it should be
I have an app that I'm building and signing and deploying for the Mac App Store. I received an email that there were problems with the deployment that make no sense to me. ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '367****Y2.com.foo.foo-one.electron' for key 'com.apple.application-identifier' in 'Foo One.app/Contents/MacOS/Foo.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libEGL.dylib' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . Say what now? This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . But that is exactly what it is set to: 367****Y2.com.foo.foo-one.electron (asterisks just here to obscure our actual TeamID) I have no idea how to proceed. Any advice? Similar to this question thread 6984
3
0
1.6k
Jul ’22
ITMS-90562: Invalid Bundle with Xcode 13.3 RC
When archiving and uploading a build of our tvOS app to App Store Connect with Xcode 13.3RC, it gets rejected with TMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path. When archiving and uploading with Xcode 13.2.1 the build is accepted and processed. I could not find any rpath issues when inspecting the binary with otool -L and otool -l. Has anyone else experienced the this issue with Xcode 13.3RC? I've filed feedback FB9952607
36
0
12k
Mar ’22