“ITMS-90158”

I recently upgraded my project's deployment target version to iOS 12.0 and started getting warnings saying: ITMS-90747: Architecture incompatible with MinimumOSVersion. The app bundle at 'MyProject.app/PlugIns/StickerPack.appex' specifies a MinimumOSVersion of '12.0' but contains a 32-bit architecture that is unsupported on iOS 12 and later. I did some research and found a few people having the same issue, one common suggestion is to lower the project's deployment target version, this isn't possible for the main target because I have a few libraries that have minimum OS version requirements. So I wonder what should be the right way to fix this, so far I can think of two solutions: The Message Extension target's Architectures is currently $(ARCHS_STANDARD) which translates to (arm64, armv7), so I can change it explicitly to arm64 only, or add armv7 to Excluded Architectures which sounds better. Change the iOS Deployment Target to some version lower and do this only for the Message Extension target. I'

I got this error while attempting to upload to test flight:ERROR ITMS-90502: Invalid Bundle. Apps that only contain the arm64 slice must also have 'arm64' in the list of UIRequiredDeviceCapabilities in Info.plist.I searched around I found solutions including:Setting Build Active Architecture to Yes (didn't affect since my project only supports arm64)Changing Archive Build Configuration to Release (already did)Unplug the device from my mac when Archiving (I am already praying to the machine spirits by this part)Lastly,Adding UIRequiredDeviceCapabilities with item arm64 to all target's info.plist This is the one I am troubled with. It is most certainly what the error requires me to do but I did for every info.plist I can find in my project. Including the main one created automatically when I created my project, one for each test build(not sure if needed just did anyway), one for the everyday widget extension my app has, one for every framework I used added via cocoapods (I edited the podfile to do it b

I'm absolutely certain this is just a result of me missing something very obvious, but I keep getting a string of errors when uploading from Xcode 11. All my icons are in place, but the errors are asking for alternative sizes ( i.e. 54 x 40, 148 x 100), that are even listed in the app icon location. I ended up switching back to an older version of xcode, and it uploaded just fine. But I would really like to sort this out so I can use the most recent Xcode in the future. I also get an Error ITMS- 90642: Missing Info.plist Key, for some reason. Again, had none of these errors in the previous xcode.

We have an app that we had in TestFlight, submitted a version for release, was approved, and had the build in state waiting for developer release. In the meantime, our TestFlight build is about to expire, and will expire before we are ready to release the app to the App Store. Every time I try to upload a new version of the app, I get the error ITMS-90129: The bundle uses a bundle name or display name that is already taken. I've tried just abut everything I can think of: I changed the bundle versions (from 1.0 to 1.0.1, and incremented the build number). I cancelled the build that was pending developer release. I still get the same error. I've confirmed that the bundle ID and display name are the same as the ones for the build we had submitted for approval previously.

<main> DBG-X: parameter FilesToUpload = [metadata.xml, JS.ipa]<main> DBG-X: parameter MinimumFileSizeThresholdForCheckum = 104857600<main> ERROR: ERROR ITMS-90161: Invalid Provisioning Profile. The provisioning profile included in the bundle com.jschat.jschatapp [Payload/JS.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal.<main> DBG-X: The error code is: 1102<main> INFO: Done performing authentication.<main> DBG-X: Returning 1First thanks to viewing my issue.I dont know why i'm facing this issue i have created the provisioning file according to the apple documentation.My app is done just to upload on app store.Please help me as soon as possible.I shall be very thankful to you.Thanks

Can anyone tell me what is causing the following ITMS error:[2018-09-15 21:12:14 CEST] <main> ERROR: ERROR ITMS-6000: Unknown or unsupported package version [software5.10].[2018-09-15 21:12:14 CEST] <main> DBG-X: The error code is: 1102I'm using XCode 9.4.1 and the included Application Loader 3.7.1.Edit: Version 5.10 is now supported, the upload now also works with 5.10 🎉

I get the folling error when trying to upload an app to TestFlight with an iMessage stickers extension with XCode 8.0 beta 3:ERROR ITMS-90644: Missing Image Asset. Your app is missing the Large App Icon asset 'iMessage App Icon' in 'Payload/App.app/PlugIns/StickerPackExtension.appex'.Is ITC accepting TestFlight builds at the moment, or is there something wrong with my extension? I've allocated images to every space in my iMessages App Icon in my .xcstickers bundle.I did notice though that the various settings images and the 1024x768 iMessages App Store image don't make it through to the built .appex file though.

I have built a framework for my app setting supported minimum OS version to 7.0. I was able to build successfully & integrate with my iOS app.Even the App Store validation phase went through successfully.At the time of uploading the binary to AppStore, i got this error - 'ERROR ITMS-90362: Invalid Info.plist value. The value for the key 'MinimumOSVersion' in bundle/Frameworks/xyz.framework is invalid. The minimum value is 8.0'Now, I am forced to update my minimum OS version to 8.0If only Xcode had suggested this at the compile time that the minimum OS version is 8.0, it would have saved my effort in building & validating the binary.Can Apple fix this in XCode 7 ?

ITMS - 90338: Non -public API usage - The app references non-public selectors in xfApp1.iOS: accessibilityBrailleMapRenderRegion, accessibilityBrailleMapRenderer, activePlayer, beginAuthorizationWithRequest:, cancelAuthorizationWithRequest:, checkFocusGroupTreeForEnvironment:, commissioningComplete:, connectionTypesMask, pairDevice:address:port:discriminator:setupPINCode:error:, playerId, serviceExtensionWillTerminate, session:didReceiveData:fromPlayer:, session:didReceiveMessage:withData:fromPlayer:, session:player:didChangeConnectionState:, session:player:didSaveData:, setAccessibilityBrailleMapRenderRegion:, setAccessibilityBrailleMapRenderer:, setConnectionTypesMask:, setListenPort:, sharedController, sleep:, test:, toggle:. 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 inclu

We got an error, when we tried to upload new build to itunesconnect via Xcode 8 (from App Store and from http://developer.apple.com/download/more/ — the same behavior). We use Swift 2.3 in our project and some pods.ERROR ITMS-90596: Invalid Bundle. The asset catalog at 'Payload/***.app/Assets.car' can't be read. Try rebuilding the app with a non-beta version of Xcode and submit it again.Any ideas? 😕

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.

Hi, Our project utilizes push notifications via OneSignal SDK. Everything looks correct and conforms with the documentation: The Push Notifications capability is enabled in XCode. The entitlements do contain the aps-environment key with the production value. I unpacked the resulting IPA and explored embedded.mobileprovision file - it does contain the aps-environment key with the production value in the Entitlements section too. The App ID and provision profiles used do include the Push Notification capability. So there's literally nothing to fix. Despite of that, when uploading the IPA to AppStore Connect, we receive an email with the warning ITMS-90078: Missing Push Notification Entitlement... that says there's no aps-environment entry. Moreover, the OneSignal dashboard indicates Missing Push Capabilities for all the iOS devices that run our application. Consequently, the push messages are not received. What could be wrong with the IPA and where to look at? Thanks in advance!

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?

Trying to upload an iOS26 app archive with Xcode 26 beta 7 and getting ITMS-90717: Invalid large app icon, meaning my app is not eligible for TestFlight testing. My App contains an IconComposer .icon asset, so I'm not sure what it's complaining about. I'm not seeing anything in the release notes about this, and I'm not sure if I'm doing something wrong or not.

When putting my IPA file into Application Loader, I get these two error messages. I was able to fix the icons the message was talking about, I just had to resize them, I did so by going into my zip file, was this the correct thing to do?Also, once I have resized them, do I completely need to redo my whole IPA file? And if so how do I do that? I've been using phonegap to develop an iPhone app.Thank you