ITMS-90158

Hello, I'm trying to submit an app to apple connect that is build outside of xcode but I'm getting this email saying the files have an invalid signature. I'm doing a step wrong or maybe using the wrong signature but not sure what is supposed to be the way to do it. The app is written with python and pyside, and packaged with pyinstaller. In the pyinstaller .spec file I set the codesign_identity and entitlements_file and also fill some things to the info_plist (CFBundleVersion, LSApplicationCategoryType, etc). This results in a .app file, which then I run a command on it: productbuild --component path/to/file.app /Applications path/to/file.pkg --sign And then push with: xcrun altool --upload-app path/to/file.pkg --type macos -u -p I'm able to upload but then I get the email with the signature error (ITMS-90238: Invalid Signature). Are these steps ok, or something else is needed?

We've started hitting this limitation when submitting builds using Xcode Cloud. ITMS-90382: Upload limit reached - The upload limit for your application has been reached. Please wait 1 day and try again. We generate TestFlight builds for every PR (builds from PR get sent to QA & devs) & for every merge (builds get sent to everybody in the team). Is there any way to know what's the limit so we can try to work around it? Edit: I've just checked, and TestFlight only reports 19 builds that are expiring in 90 days (aka were uploaded within the last 24h). Is the limit that low?

Getting this error while submitting app to the TestFlight. ITMS-90338: Non-public API usage - The app references non-public selectors in ***: initWithURLStrings:. 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. I didn't get any idea about this.

Good morning. After a new submission (same project, no breaking changes) we have received a strange error. ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/ProjectLIB.framework/ProjectLIB: connectionState, initWithURLStrings:. 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. The ProjectLIB (the correct name is omitted) is a framework library deployed also in another App, and this App has been validated and correctly deployed under Testflight versions. So we are a little bit confused about the different validation of the two applications, with the same ProjectLIB.framework inside. The only difference is that the wrong one is built with Unity. How can we make changes to be compliant to Apple

I'm testing the tvOS version of the development app (swiftUI), and I need to add the Intents Extension to the target to support Siri intents (INPlayMediaIntent) to play music, this is already working fine in the iOS version of the project and submitted for testing, when I compile and submit Go to App Store Connect, and then there is the following error in the feedback email: ITMS-90898: Invalid Mach-O entry point - Please make sure the build system passes “-e _NSExtensionMain” to the linker for the “MusicPlayer tvOS.app/PlugIns/TVSiriControlAudioExtension.appex” extension bundle, or the extension will not function. My project has Siri enabled, but I don't know what to do now. I tried to delete and re-create the Intents Extension without making any changes to the file, and submitted it directly to App Store Connect, but still prompted this error. Headache

Dear Developer, We identified one or more issues with a recent delivery for your app, AisleGo Weddings 2.1.8 (6). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in AisleGo: _isKeyDown, _modifiedInput, _modifierFlags. 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 We already have our application production, nothing changed this time, now changed dev REST APIs endpoint to Prod and uploading on the test flight for App store release but getting this error upon test flight.

We received this message after uploading IPA to App Store Connect: Dear Developer, We identified one or more issues with a recent delivery for your app, **** 2.4.1 (4). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in Onay: _setWidth:. 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 We tried to rename all methods or delete them and republish, but always receive this message. Can we get more detailed error description?

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/ They haven't mentioned Non-public APIs which we have used how can we resolve it? How can we resolve with this information?

Hi, I am trying to run xcrun altool --list-providers -u my@email.com -p my-application-specific-password My console response looks as follows with a -24169 error when trying to authenticate. I have used this application password in the past with fastlane, but I do not seem to be able to authenticate today. 2023-02-17 10:09:28.753 Initializing bundle from: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework 2023-02-17 10:09:28.762 Will look for transporter at executable bundle relative path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2023-02-17 10:09:28.762 Looking for Transporter at path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2023-02-17 10:09:28.762 Looking for Transporter at path: /Applications/Xcode.app/Contents/Developer/usr/bin/../SharedFrameworks/ContentDeliveryServices.fra

I have a Mac app that was accepted to the App Store when I built it using Xcode 13 (with code signing set to automatic, just like I do now), but with Xcode 14.2 I keep getting mails with ITMS-90288: Invalid Code Signing Entitlements and TMS-90286: Invalid Code Signing Entitlements, two very similar errors for each embedded dynamic library. The exact wording is this: TMS-90288: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '(My team id).' for the key 'com.apple.application-identifier' in 'Spatterlight.app/Contents/Frameworks/libc64diskimage.dylib' ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '(My team id).' for key 'com.apple.application-identifier' in 'Spatterlight.app/Con

Problem Description: ipa trial, get feedback from Apple ITMS-90620: Invalid iMessage App - Your iMessage app contains an invalid sticker pack. The app may have been built or signed with non-compliant or prerelease tools. For more information, go to developer.apple.com. Since we added sticker (Messages Application Extension) we checked There is no problem with bundleid of ipa and bundleid of sticker We found that hxl.xcarchive contains the MessagesApplicationExtensionSupport folder, and there is a file named MessagesApplicationExtensionStub in it But we did not include the MessagesApplicationExtensionSupport folder after exporting ipa from hxl.xcarchive Our command line to export ipa is: xcodebuild -exportArchive -archivePath build/20230203_130051/hxl.xcarchive -exportPath build/20230203_130051/ -exportOptionsPlist ExportOptions.plist

While attempting to upload my app to TestFlight (which has already been uploaded numerous times, including just a few days ago with the same code base) there is this error TMS-90338: Non-public API usage - The app references non-public selectors in : _isKeyDown, _modifiedInput, _modifierFlags..... Nothing new there, that's been happening for months for myself and countless others and has been reported numerous times, i.e. https://developer.apple.com/forums/thread/127678?answerId=715975022#715975022 https://developer.apple.com/forums/thread/714450 But now there's a difference - in the past the builds always appeared in Testflight after getting this warning, so it wasn't an issue. But now that's changed, the build is no longer appearing in Testflight, so it suddenly is a very big issue.

I built and submitted a react-native app and the app was sent to Apple for submission. I received an email back 5 minutes later that reads Dear Developer, We identified one or more issues with a recent delivery for your app, TYPSA REGISTRO DE JORNADA 1.0.2 (1.4). Please correct the following issues, then upload again. ITMS-90748: ${message} Best regards, The App Store Team The ${message} looks like a template placeholder that isn't populated and thus there is no information indicating what might be wrong. I google searched for the specific error code and could not find anything. What does this code mean and why is my app submission failing?