Search results for

ITMS-90158

1,685 results found

Post

Replies

Boosts

Views

Activity

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
98
3w
ITMS-91065: Missing signature and forks of open source libs
Hello, I received an App Store rejection (ITMS-91065: Missing signature) for one of my iOS apps related to vendor-signed third-party SDKs and I want to understand the rule more clearly. My understanding is that some third-party SDKs must be vendor-signed; I believe the vendor list is: https://developer.apple.com/support/third-party-SDK-requirements/. In my app, for example, I have a fork of RxSwift that we build from source and therefore self-sign. That seems reasonable, but it does mean that it will no longer be signed by the vendor. How can I ensure I won't be flagged for using a non–vendor-signed third-party SDK in this case? Thanks, Sam
Topic: App Store Distribution & Marketing SubTopic: App Review
0
0
91
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
201
Jan ’26
XCode Cloud Signing Error
As mentioned in the linked post, I can archive the project locally but not via Xcode Cloud. I have also created a new project, but the same thing happens here. https://developer.apple.com/forums/thread/746210 Error Code: ITMS-90035: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{AppName}.app/{AppName}” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
0
0
272
Dec ’25
Reply to ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it
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:
Dec ’25
Reply to ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it
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:
Dec ’25
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 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:
2
0
185
Dec ’25
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
252
Dec ’25
Reply to 90714: Invalid binary.
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:
Nov ’25
App Rejection ITMS-91061: SDK Provider "Unity Technologies" Has Not Signed Privacy Agreement
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
1
0
93
Nov ’25
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
141
Nov ’25
ITMS-90034: Missing or invalid signature
We are currently facing an issue when attempting to deploy or update the iOS application provided by Salesforce. When signing the .ipa file shared periodically by Salesforce using Company’s Apple certificates, and attempting to upload it via Apple’s native Transporter application, we receive the following error message: ITMS-90034: Missing or invalid signature – The bundle 'com.mysalesforce.mycommunity.[CODE]' at bundle path 'Payload/CommunitiesApp.app' is not signed using an Apple submission certificate. We have strictly followed the steps described in the Salesforce document https://quip.com/yBxiAS29ZlvI We have reviewed the Apple certificates. They are the same ones currently used for other active Company's applications — valid, unchanged, and not expired.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
0
0
50
Oct ’25