“ITMS-90338”

I'm an indie developer. My latest minor update for my game which has been on the Mac App Store for 13 years and which has spent time at #1 on the download charts just started getting rejected for the following reason: Guideline 2.5.2 - Performance - Software Requirements The app installed or launched executable code. Specifically, the app uses the itms-services URL scheme to install an app. However my app is certainly not installing any apps and to the best of my knowlege it is not using any itms/itunes/etc. type URLs in any way, so I can't figure out what would be triggering this claim. Inquiries as to what app I am supposedly installing or what URL I am supposedly using have yielded 'no further information can be provided'. Has anyone run into something similar? Any ideas on obscure scenarios that could trigger this particular rejection? Or any advice on what one should do in my situation? I feel a bit stuck. Has anyone had luck with the appeal process for this sort of thing (to at least g

We were able to validate and upload a mac arcade build to ASC, but when submitting it for review we got this message from Apple: ITMS-90812: Arcade static library missing or not correctly linked. The app does not link against the library performing the Arcade subscription check. I've never seen this error message before. For context, we recently upgraded to Unity 2020 to support Apple silicon. The build launches and runs without any issues so not sure how to address the issue. FYI 'Mac Store App Validation' is checked in the build settings. Any help would be appreciated!

I suddenly started to receive the following email with the error in it stating that my uploaded app is not available to be used in TestFlight: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at “MyApp.app/Contents/PlugIns/MyAppWidgetExtension.appex” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' It was all working fine and now I am not sure even where to start looking. Signing, provisioning and everything else is managed automatically.

Hey There, I'm trying to build a project on github, so I can get it working in testflight. The project can be found here: https://github.com/coderjoris/StructureScannerSwift I've downloaded it, added icons and all that good stuff and now I'm trying to archive and upload it. I can't seem to find out how to modify the project so it will submit successfully, I keep getting an email follow up with: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. My submission steps are as follows: clean the build folder Product > Archive Then I follow the prompts to upload to the app store. Trying to fix the issue, I've tried every single recommendation I can find on the internet, and nothing seems to fix it. Some examples: updated OS and Xcode to their most recent versions toggled Always Embed Swift Standard Libraries between Yes/No for both project and target tried using the deprecated build system to build etc..

Hi guys, need some help on this issue when I submit my testing app to TestFlight using GitHub Actions and Fastlane, I get this warning from App Store Connect: We noticed one or more issues with a recent delivery for the following app: Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. I am using React Native CLI, and Fastlane to run and build my app through Github Actions. After scouring around, from what I understood was that all I needed to do was just to update my Xcode and iOS SDK to the latest, which I did. Currently my Xcode is 15.2 and iOS SDK is on 17 already. However, I still receive this warning w

ITMS-90334: Invalid Code Signature Identifier - The identifier 'bundle id followed by 30 random characters' in your code signature for 'bundle id' must match its Bundle Identifier 'bundle id' Currently, any app I’ve tried is getting this error when submitting from the app. I’ve got all the places where you put the name, the sku, and bundle id set with the same value (copy/paste), and I’ve tried different variations, but now that long string of random characters is appended and I can’t use TestFlight. Maybe because this is a beta iPad OS? Been on a beta for what seems like forever. It’s worked in the past. Great. Totally innocuous post that has something that is not permitted. Be nice if you TELL me what’s NOT PERMITTED!

Older version of xcode 14.3.1 is uploading build with notice to update xcode version but newer version of xcode 15.3.1 and beta giving the error below. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Shared.framework/Shared: _SSL_CTX_free, _SSL_CTX_new, _SSL_CTX_set_alpn_protos, _SSL_CTX_set_options, _SSL_do_handshake, _SSL_free, _SSL_get0_alpn_selected, _SSL_get_error, _SSL_get_session, _SSL_new, _SSL_read, _SSL_set_alpn_protos, _SSL_set_bio, _SSL_set_connect_state, _SSL_write. 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.

Hi there.I'm developing a mobile application on both iOS and Android platforms, using Ionic Framework.I make all certificates by following http://docs.ionic.io/docs/ios-build-profiles, they look all good and compilation with Ionic is successful.Then I upload the .ipa file via Application Loader to make it available on TestFilght.The last build was made on march 18th 2016 with no issue, but Application Loader rejects my build today :✖ ERROR ITMS-90034: Missing or invalid signature. The bundle 'com.ionicframework.oenobook841275' at bundle path 'Payload/Oenobook.app' is not signed using an Apple submission certificate.I tried to recreate every certificate (for distribution), they're all green in my keychain and Developer account.I went back on a previous build thanks to Git.I even did format my Mac, so everything I can use is up to date.Help. 😢

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