ITMS-90158

I really need help. Can anyone decrypt the following message for me: Dear Developer, We identified one or more issues with a recent delivery for your app, MYAPP 2.0 (1200). Please correct the following issues, then upload again. ITMS-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: '' for the key 'com.apple.application-identifier' in 'MYAPP.app/Contents/Frameworks/libsqlite3s.dylib' ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '' for key 'com.apple.application-identifier' in 'MYAPP.app/Contents/Frameworks/libsqlite3s.dylib' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . The 2 dylibs

After using iOS16's new feature AppIntents, AppStore review is failed: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. I tried all methods in internet, but they all not work. Such as: I'm using the public version of Xcode I'm not using Ad hoc cert or .pp file I tried archive manually without using fastlane I tried change the Always Embed Swift Standard Libraries The only changes is iOS16's AppIntents. Before i use AppIntent, it works fine. After i use AppIntent, it failed. Only one commit between 2 .ipa. Can anyone help me? Many thanks.

I received an email with the following message from Apple: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Well, what's the problem Apple? I used 15.5. That's later than 15!

While deploying the apps to app store connect, I am getting a mail from app store connect stating: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. For context, my minimum deployment version is set to 15.0 and building the apps with xcode 13.4 (ios 15.5). Can anyone please help me with this.

We got this message after publishing our app to test flight: ITMS-90725: SDK Version Issue - This app was built with the iOS 16.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. I'm no math genius but am pretty sure that 16 is greater than 15. Why did I get this messages? Can I ignore it? will it prevent my app from being able to be submitted to the app store?

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