ITMS-90158

I am trying to submit my updated iOS app via application loader but I keep getting an SDK Version Issue. ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 8.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later. My apps are built from a third party but unfortunately they do not support anymore. Is there a way to rebuild the app using command line tools. I searched and tried to build using xcodebuild command but nothing seems to work. Is there an alternative?

Howdy,I've got an iOS 9 + watchOS 2 app I'm trying to upload to iTunesConnect. I'm using Xcode 7 (Organizer) and not the separate Application Loader app. There are other errors present, but the one that looks particularly interesting is:ITMS-90081 Applications built for more than one architecture require a iOS Deployment Target of 3.0 or later.The only target that isn't iOS9 is, interestingly enough, watchOS 2.0 in the Watch App and Watch Extension targets. Googling around the 3.0 or later hasn't been mentioned in many years - I'm wondering if there's some glitch in the code that is recognizing watchOS 2.0 as <3.0.Has anyone else been able to successfully upload a watchOS 2 app?Joe

I'm not sure what type of provisioning profile I need to create for my Mac App to allow TestFlight. I am archiving the app through Xcode and allowing it to control the provisioning but it still does not work.

My application always fails to upload due to this Error message: Incorrect Platform. You Included arm64 executable /app name/ in your iOS bundle. The app only targets armv7 devices and all extensions and targets are set to armv7. Just out of curiosity I created a empty Xcode project and without any modifications tried uploading it again. The same result... has anyone got an idea how I could solve that? I am using Xcode 12 and the transporter app to upload because Xcode is not working

Our app submission is being rejected with the following error message: TMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. We have thoroughly scanned our code and all dependent libraries for references to UIWebView and found none. looking for help, on how to address this issue

Hi all, I was having an issue which my APP was got rejected and I received an email said the following ITMS-90165: Invalid Provisioning Profile Signature. The provisioning profile included in the bundle 'app' (ios.app) cannot be used to submit apps to the iOS App Store until it has a valid signature from Apple. (Expired profile signing certificate.) However, I can see my certificate and profile are still valid till 2022 May from the developer portal. Can someone let me know why I encounter this issue please? I was able to submit an iOS APP back in 2022 Mar. Could anyone please advise what I need to do to resolve the current situation and how I can prevent the same case in ongoing please? Also, it will be great if anyone can let me know any limitation or standard of using the APPLE related certificate to do distribution and development.

Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?

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'm trying to upload a version with Compose multiplatform dependencies, and I get an email: 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 Nanit: _ubidi_close, _ubidi_getDirection, _ubidi_getLength, _ubidi_getLevelAt, _ubidi_openSized, _ubidi_reorderVisual, _ubidi_setPara, _ubrk_clone, _ubrk_current, _ubrk_first, _ubrk_getRuleStatus, _ubrk_getRuleStatusVec, _ubrk_isBoundary, _ubrk_last, _ubrk_next, _ubrk_previous, _uloc_getDefault, _uloc_toLanguageTag, _uscript_getScript. 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. When I run the validation from Xcode it works. Can you please advice?

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

I keep getting emails saying my app cant be processed, how can I fix it or find out whats causing it. Dear Developer, We identified one or more issues with a recent delivery for your app, EmbryosIOS 0.1 (0.99). 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

Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app '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.' Here is my packaging process: Generate an app using the electron packager tool Sign the app using @ electron

In our IOS app, we have few libraries that do not spport BITCODE so we had ENABLE_BITCODE set to NO for the iOS APP and Yes for the Watch App.And, this setting has worked for us in the past but now we are getting error during submission. ERROR ITMS-90635: Invalid Mach-o formatThe Error descriptions mainly says that all targets for a platform should have a consistent value of ENABLE_BITCODE.Is bitcode now required for iOS Apps too if we have a Watch App?