Search results for

“ITMS-90158”

1,691 results found

Post

Replies

Boosts

Views

Activity

ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
Hello, after updating to Xcode 26.4.1, our app is rejected on App Store Connect because of the following error: ITMS-90429: Invalid Swift Support - The files libswiftCompatibilitySpan.dylib aren’t at the expected location /Payload/AlbusAir.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. We did not change anything to the code, we didn't update any dependency. As far as I'm aware, we don't use Spans in Swift. I even tried copying the dylib myself in the app in a Xcode build phase and it still doesn't work. Can someone help? Thanks !
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
7
0
258
3w
The right way to extend UIRequiredDeviceCapabilities
I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from armv7 to armv7 nfc. This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?
Topic: App & System Services SubTopic: General Tags:
3
0
1k
4w
Reply to ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
You didn't miss a think and it seems you are using the latest Xcode and still producing the ITMS-90429 error without moving the framework. Very weird. But we should get to the bottom of the issue. May I ask you to file a bug? nce you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert
  Worldwide Developer Relations.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Apr ’26
Reply to ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
I am using Xcode 26.4.1 (17E202). To copy the dylib, I am using a custom made Xcode build phase. I opened the resulting IPA to check, and the .dylib is present in Payload/AlbusAir.app/Frameworks/libswiftCompatibilitySpan.dylib. I put it here because the ITMS-90429 error told me that the file is expected in /Payload/AlbusAir.app/Frameworks. I checked the thread that you linked but I don't see any useful answer made to the OP, did I miss something? Thanks for your help !
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Apr ’26
Reply to ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
Thanks for the post. This normally occurs when updating to newer versions of Xcode as swift support requirements, the validator checks the swift the executables from Frameworks folders in the app, and makes sure that the names match 1 to 1. The libswiftCompatibilitySpan.dylib library. The ITMS-90429 error triggers because App Store Connect is extremely strict about how Swift dynamic libraries are packaged inside your exported .ipa file. What version of Xcode are you using? When you manually copy the .dylib into the app's Frameworks folder, it fails App Store validation because Apple requires Swift libraries to exist inside the folder at the root of the .ipa archive. Are you manually doing that? Or are you are using CocoaPods? I would recommend to also check this thread https://discussions.apple.com/thread/256135560?sortBy=rank Albert
  Worldwide Developer Relations.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Apr ’26
Reply to Apple managed asset pack for FoundationModels adapter on Testflight does not download (statusUpdates silent)
Thanks for the answer! Update: First, I've found out that i was packaging the .aar file using the generic xcrun ba-package package tool, instead of using the FoundationModels adapter-specific one, xcrun ba-package foundation-models package (found out from the adapter training toolkit source - produce_asset_pack.py), as the FoundationModels runtime recognizes only packs built with the FoundationModels tool. The issue is that the FoundationModels tool generates a manifest with the property onDemand set to null (onDemand: null) , which gets rejected by Transporter when trying to upload it (I was getting ITMS-91140 - invalid manifest file). I tried extracting the .aar, changing null to {} in manifest.json, then repacking the .aar file with the archive command - after doing this, the upload via Transporter was successful and accepted in App Store Connect. The internal TestFlight delivery works and the statusUpdates stream fires all events correctly (.began/.downloading/.finished). Hope this will help anyo
Topic: Machine Learning & AI SubTopic: Foundation Models Tags:
Apr ’26
App alternative icon not working when archieve.
I add the following info in the build settings of my app. Then I also add the icon to my asset. I build the app, it works normally, but I notice that when I changed the icon to 'AppIcon-Defaults', The icon change alert didn't appear. but it succeeds . I uploaded the archive to App Store I got: ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-Defaults” that references asset “AppIcon-Defaults.” No such asset is present in the asset catalog. Then I use xcrun --sdk iphoneos assetutil --info Assets.car to check the assets inside the archieved app, It have the asset.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
638
Feb ’26
ITMS-90426: Invalid Swift Support
Hi,Having issues uploading our build to App Store Connect for use in TestFlight. We get a success when building through Xcode, but we get an email after it uploads via archive manager stating ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.. We have confirmed that we don't have any Swift dependencies and that we are running the latest Xcode (v11.3.1). We've also tried to build/deploy this on multiple computers with the same error. Our app was built using Unity, then brought into Xcode to build/deploy from there. We have never had any Swift dependencies in our project. We are able to deploy directly to our devices, but it seems that the only time we run into issues is trying to. Any help is appreciated.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
8
0
15k
Feb ’26
ITMS-90426: Invalid Swift Support
Good day, I've uploaded a build to TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our project started in Objective-C and have mixed swift class and pods. The last uploaded build without any automated response was Nov 8, 2023. I'm using XCode Version 26.0.1 (17A400). I've tried every way i found in internet and i'm not able to find any solution for this. ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES use_frameworks! :linkage => :dynamic (in pods) We would appreciate any assistance in clarifying why this issue is occurring and how we should proceed to address it. Your guidance would mean a lot. Thank you.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
1
0
197
Feb ’26
ITMS-90118: Invalid routing app setting:
Hi everyone, I’m running into an App Store Connect issue that seems to be a misclassification, and I’m hoping someone (or Apple staff) can help clarify or advise. App: Quick Quote Calculator Platform: iOS (built with Expo) App type: Business No navigation, routing, maps, or turn-by-turn directions When submitting a new build, App Store Connect returns: ITMS-90118: Invalid routing app setting To upload a routing app coverage file, you must define the app binary as a routing app. However: There is no “Routing & Navigation” section in App Information There is no “Routing App Coverage File” section under App Store No routing metadata or coverage file has ever been uploaded The app does not provide routing or navigation functionality It appears the binary itself is being classified as a routing app, but there is no UI in App Store Connect to view or remove this classification. What I’ve tried Verified app metadata and screenshots Confirmed no routing/navigation APIs are used Reviewed Info.plist permis
Topic: App & System Services SubTopic: Maps & Location
1
0
217
Jan ’26
Purchase Intent does not work when app has been launched
I'm implementing PurchaseIntent.intents for App Store in-app purchase promotions, following Apple's WWDC guidance. The API only works on cold launch (killed→launch), but fails on background→foreground transitions, making App Store promotions unusable. Sample code as followed from WWDC23 video What's new in StoreKit 2 and StoreKit Testing in Xcode. In the StoreKitManager observable class, I have this function which is initialized in a listening task: func listenForPurchaseIntent() -> Task { return Task { [weak self] in for await purchase in PurchaseIntent.intents { guard let self else { continue } let product = purchase.product await self.purchaseProduct(product) } } } where purchaseProduct() will perform the call to: try await product.purchase() ISSUE: When the app is in background (after previously launched), and the purchase intent is initiated from Xcode Transaction Manager or using the itms-services://?action=purchaseIntent method, the system foregrounds my app but the purchase intent is never
Topic: App & System Services SubTopic: StoreKit Tags:
3
0
259
Jan ’26
ITMS-90555: On-Demand Resources exceed 30GB after App Thinning – Need clarification on variant size calculation
Hello, I am encountering the following error when uploading a build to App Store Connect: ITMS-90555: Thinned app size is too large – Your on-demand resources in the universal variant are 30 GB, which exceeds the maximum allowable size. After app thinning, the total size of your on-demand resource asset packs in any variant must be less than 30 GB. Our application includes a large amount of font resources delivered via ODR. Before making structural changes, I need clarification because the documentation does not fully explain how ODR size calculations work per variant. Environment Xcode: (latest stable) Distribution method: App Store submission ODR total size before thinning: approximately (28 GB) Build processing fails immediately with the ITMS-90555 error Questions How exactly does App Thinning compute the size of ODR asset packs per variant? Is ODR size evaluated: Per device-specific variant, Or is the “universal variant” treated as an additional variant that must independently stay under
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
2
0
351
Jan ’26
ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
Hello, after updating to Xcode 26.4.1, our app is rejected on App Store Connect because of the following error: ITMS-90429: Invalid Swift Support - The files libswiftCompatibilitySpan.dylib aren’t at the expected location /Payload/AlbusAir.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. We did not change anything to the code, we didn't update any dependency. As far as I'm aware, we don't use Spans in Swift. I even tried copying the dylib myself in the app in a Xcode build phase and it still doesn't work. Can someone help? Thanks !
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Replies
7
Boosts
0
Views
258
Activity
3w
The right way to extend UIRequiredDeviceCapabilities
I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from armv7 to armv7 nfc. This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?
Topic: App & System Services SubTopic: General Tags:
Replies
3
Boosts
0
Views
1k
Activity
4w
Reply to ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
You didn't miss a think and it seems you are using the latest Xcode and still producing the ITMS-90429 error without moving the framework. Very weird. But we should get to the bottom of the issue. May I ask you to file a bug? nce you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert
  Worldwide Developer Relations.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Replies
Boosts
Views
Activity
Apr ’26
Reply to ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
I am using Xcode 26.4.1 (17E202). To copy the dylib, I am using a custom made Xcode build phase. I opened the resulting IPA to check, and the .dylib is present in Payload/AlbusAir.app/Frameworks/libswiftCompatibilitySpan.dylib. I put it here because the ITMS-90429 error told me that the file is expected in /Payload/AlbusAir.app/Frameworks. I checked the thread that you linked but I don't see any useful answer made to the OP, did I miss something? Thanks for your help !
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Replies
Boosts
Views
Activity
Apr ’26
Reply to ITMS-90429: Invalid Swift Support on libswiftCompatibilitySpan.dylib after update to Xcode 26.4.1
Thanks for the post. This normally occurs when updating to newer versions of Xcode as swift support requirements, the validator checks the swift the executables from Frameworks folders in the app, and makes sure that the names match 1 to 1. The libswiftCompatibilitySpan.dylib library. The ITMS-90429 error triggers because App Store Connect is extremely strict about how Swift dynamic libraries are packaged inside your exported .ipa file. What version of Xcode are you using? When you manually copy the .dylib into the app's Frameworks folder, it fails App Store validation because Apple requires Swift libraries to exist inside the folder at the root of the .ipa archive. Are you manually doing that? Or are you are using CocoaPods? I would recommend to also check this thread https://discussions.apple.com/thread/256135560?sortBy=rank Albert
  Worldwide Developer Relations.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
Replies
Boosts
Views
Activity
Apr ’26
Reply to Apple managed asset pack for FoundationModels adapter on Testflight does not download (statusUpdates silent)
Thanks for the answer! Update: First, I've found out that i was packaging the .aar file using the generic xcrun ba-package package tool, instead of using the FoundationModels adapter-specific one, xcrun ba-package foundation-models package (found out from the adapter training toolkit source - produce_asset_pack.py), as the FoundationModels runtime recognizes only packs built with the FoundationModels tool. The issue is that the FoundationModels tool generates a manifest with the property onDemand set to null (onDemand: null) , which gets rejected by Transporter when trying to upload it (I was getting ITMS-91140 - invalid manifest file). I tried extracting the .aar, changing null to {} in manifest.json, then repacking the .aar file with the archive command - after doing this, the upload via Transporter was successful and accepted in App Store Connect. The internal TestFlight delivery works and the statusUpdates stream fires all events correctly (.began/.downloading/.finished). Hope this will help anyo
Topic: Machine Learning & AI SubTopic: Foundation Models Tags:
Replies
Boosts
Views
Activity
Apr ’26
App alternative icon not working when archieve.
I add the following info in the build settings of my app. Then I also add the icon to my asset. I build the app, it works normally, but I notice that when I changed the icon to 'AppIcon-Defaults', The icon change alert didn't appear. but it succeeds . I uploaded the archive to App Store I got: ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-Defaults” that references asset “AppIcon-Defaults.” No such asset is present in the asset catalog. Then I use xcrun --sdk iphoneos assetutil --info Assets.car to check the assets inside the archieved app, It have the asset.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
3
Boosts
0
Views
638
Activity
Feb ’26
ITMS-90426: Invalid Swift Support
Hi,Having issues uploading our build to App Store Connect for use in TestFlight. We get a success when building through Xcode, but we get an email after it uploads via archive manager stating ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.. We have confirmed that we don't have any Swift dependencies and that we are running the latest Xcode (v11.3.1). We've also tried to build/deploy this on multiple computers with the same error. Our app was built using Unity, then brought into Xcode to build/deploy from there. We have never had any Swift dependencies in our project. We are able to deploy directly to our devices, but it seems that the only time we run into issues is trying to. Any help is appreciated.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
8
Boosts
0
Views
15k
Activity
Feb ’26
ITMS-90426: Invalid Swift Support
Good day, I've uploaded a build to TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our project started in Objective-C and have mixed swift class and pods. The last uploaded build without any automated response was Nov 8, 2023. I'm using XCode Version 26.0.1 (17A400). I've tried every way i found in internet and i'm not able to find any solution for this. ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES use_frameworks! :linkage => :dynamic (in pods) We would appreciate any assistance in clarifying why this issue is occurring and how we should proceed to address it. Your guidance would mean a lot. Thank you.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Replies
1
Boosts
0
Views
197
Activity
Feb ’26
ITMS-90118: Invalid routing app setting:
Hi everyone, I’m running into an App Store Connect issue that seems to be a misclassification, and I’m hoping someone (or Apple staff) can help clarify or advise. App: Quick Quote Calculator Platform: iOS (built with Expo) App type: Business No navigation, routing, maps, or turn-by-turn directions When submitting a new build, App Store Connect returns: ITMS-90118: Invalid routing app setting To upload a routing app coverage file, you must define the app binary as a routing app. However: There is no “Routing & Navigation” section in App Information There is no “Routing App Coverage File” section under App Store No routing metadata or coverage file has ever been uploaded The app does not provide routing or navigation functionality It appears the binary itself is being classified as a routing app, but there is no UI in App Store Connect to view or remove this classification. What I’ve tried Verified app metadata and screenshots Confirmed no routing/navigation APIs are used Reviewed Info.plist permis
Topic: App & System Services SubTopic: Maps & Location
Replies
1
Boosts
0
Views
217
Activity
Jan ’26
Purchase Intent does not work when app has been launched
I'm implementing PurchaseIntent.intents for App Store in-app purchase promotions, following Apple's WWDC guidance. The API only works on cold launch (killed→launch), but fails on background→foreground transitions, making App Store promotions unusable. Sample code as followed from WWDC23 video What's new in StoreKit 2 and StoreKit Testing in Xcode. In the StoreKitManager observable class, I have this function which is initialized in a listening task: func listenForPurchaseIntent() -> Task { return Task { [weak self] in for await purchase in PurchaseIntent.intents { guard let self else { continue } let product = purchase.product await self.purchaseProduct(product) } } } where purchaseProduct() will perform the call to: try await product.purchase() ISSUE: When the app is in background (after previously launched), and the purchase intent is initiated from Xcode Transaction Manager or using the itms-services://?action=purchaseIntent method, the system foregrounds my app but the purchase intent is never
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
3
Boosts
0
Views
259
Activity
Jan ’26
Reply to Xcode Cloud Build Failed with Preparing build for App Store Connect failed
in my case I received an email with these requirements: ITMS-90022: Missing required icon file ITMS-90023: Missing required icon file ITMS-90713: Missing Info.plist value addressing those made the trick
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
Replies
Boosts
Views
Activity
Jan ’26
ITMS-90555: On-Demand Resources exceed 30GB after App Thinning – Need clarification on variant size calculation
Hello, I am encountering the following error when uploading a build to App Store Connect: ITMS-90555: Thinned app size is too large – Your on-demand resources in the universal variant are 30 GB, which exceeds the maximum allowable size. After app thinning, the total size of your on-demand resource asset packs in any variant must be less than 30 GB. Our application includes a large amount of font resources delivered via ODR. Before making structural changes, I need clarification because the documentation does not fully explain how ODR size calculations work per variant. Environment Xcode: (latest stable) Distribution method: App Store submission ODR total size before thinning: approximately (28 GB) Build processing fails immediately with the ITMS-90555 error Questions How exactly does App Thinning compute the size of ODR asset packs per variant? Is ODR size evaluated: Per device-specific variant, Or is the “universal variant” treated as an additional variant that must independently stay under
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
2
Boosts
0
Views
351
Activity
Jan ’26
Reply to App Review Rejected, Invalid Binary, App Version
@vicatcu Awesome you found out the issue and thanks for posting that so other developers can be aware of if they get the ITMS-91061 that's what they need to do as well as posting the name of the plugin and the replacement to use. This a complete answer for developers. Thanks! Albert Pascual
  Worldwide Developer Relations.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
Boosts
Views
Activity
Dec ’25
Reply to App Review Rejected, Invalid Binary, App Version
I discovered the root cause was that a new requirement (ITMS-91061: Missing privacy manifest) started being enforced in December that affected the use of the @codetrix-studio/capacitor-google-auth. It seems like that plugin is not being maintained anymore, and I'll be looking into migrating to using @capgo/capacitor-social-login instead.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
Boosts
Views
Activity
Dec ’25