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.
Search results for
ITMS-90158
1,685 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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.
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:
Swift Packages
App Store
iOS
App Submission
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
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
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:
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
@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:
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:
We are getting the above mentioned error while uploading to TestFlight. We have used a Swift Class to request for the Age Range via DeclaredAgeRange Framework. We have exposed Swift class and a helper function to be available in Objective-C layer. We have enabled the following build settings SWIFT_OBJC_INTERFACE_HEADER_NAME = Common-Swift.h; SWIFT_OBJC_BRIDGING_HEADER = Common-Bridging-Header.h ; ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES Also we are compiling the application using latest available Xcode release 17C52 Is there anything else we need to do to resolve the error?
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Swift
TestFlight
Declared Age Range
Hi Albert I went through Ed's post; basically, he is talking about how to embed the frameworks. In our case, this isn't about embedding the frameworks we have developed or even third party frameworks. It's likely about the Swift system libraries provided by Xcode, probably to support older iOS versions. As pointed out in Ed's post - iOS, watchOS, and tvOS support third-party frameworks but don’t support third-party standalone dynamic libraries—those outside a framework bundle, typically with the .dylib filename extension. The only exception to this rule is the Swift system libraries provided by Xcode. Our application deployment target is set to 13.0. We have started using Declared AgeRange Framework (Swift ONLY API) to comply with the upcoming state law. Declared AgeRange is an asynchronous API and our application uses await/Async. Initially we encountered a TestFlight error regarding the missing SwiftSupport folder. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing We resolved t
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Thanks for the post and the details, the error is not about having the latest version of Xcode, looks like you do have it as Xcode Version 26.2 (17C52). The error message you're encountering, ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing., indicates that your app submission to App Store Connect is missing a required folder named SwiftSupport. So this is extremely interesting to me for sure. When archiving your app, ensure there are no build warnings about folders. Go to > , and then check the Organizer to ensure everything is correctly packaged. If your app uses Swift Package Manager, ensure that all packages are updated and correctly integrated. Sometimes issues arise from improperly configured packages? I believe this issue is always about packages you are using. Can you check that? read until the end where a post from an Apple engineer will give you more information. If you're manually managing your app bundle, ensure the folder is present in the archive's structure. It
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Hi When attempting to upload a React Native app (version 0.77) we encountered 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. If to check ipa folder we can see that content includes only 2 folders: Payload Symbols Could you please tell us why it does not include Swift Support folder? We tried to use XCode - 16.2 and 16.3 Thank you
Our Unity-built macOS application (developed with Unity 2020.3.36f1) was rejected from App Store Connect with reason ITMS-91061. The Apple Review Team specifically stated that the issue is that the SDK provider, Unity Technologies, has not signed the required privacy agreement with Apple. We are now seeking guidance from the Apple community or official sources: Confirmation of Agreement Status: Is there an official channel for developers to check the privacy agreement status of a specific SDK provider like Unity Technologies? Recommended Path for Developers: What is the official recommended course of action for developers facing this issue? Must we wait indefinitely for the SDK provider to complete the signing process, or is there a compliant path forward for us? Community Experience: Have any other developers using legacy versions of Unity successfully resolved this? Could you share your experience? Any guidance on how to proceed would be immensely helpful. Thank you for your support!
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Thanks for the post. Are you using any other software besides Xcode? I have a few suggestions that I would like to share with you. Additionally, I would appreciate it if you could provide as much information as possible regarding the project that is generating this issue. Regrettably, the error message does not provide a substantial amount of information. “ITMS-90714: ” Invalid binary. The application contains one or more corrupted binaries. Please rebuild the application and resubmit it. Could I kindly request a few questions to assist us in further narrowing down the issue? Are you using Objective-C with empty names in the metadata? To identify the binaries with those conditions, you can run the following Terminal command on each binary inside the app: % xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null)” Can you check the build log in Xcode and provide me with those messages including the warnings are really important and may give us a clue. Can you share those warnings? Additionally,
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: