“ITMS-90158”

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 !

Hi all, I have a build in Waiting for Beta App Review that has been stuck for more than three days, well beyond the typical 24-48 hour window. Context: • Internal-use app distributed via TestFlight only (no App Store release). • Uploaded approximately April 18, 2026. • No ITMS warnings, no rejection notice, no request for additional information. • A newer build was uploaded today (April 21, 2026). It processed correctly and is also now awaiting Beta App Review behind the older one. • I noticed another forum thread referencing FB22543589 / Case ID 102872835864, reporting TestFlight builds being flagged as Expired/unavailable overnight between April 20 and April 21, 2026. I would like to rule out whether my submission was affected by that incident. Questions: Has anyone else experienced Beta App Review delays during the week of April 20, 2026? Beyond filing a Feedback Assistant report, is there a recommended escalation path for stuck beta reviews? If my pending build was affected by the April 20-21 Tes

Hi All, Our app update got rejected with the following reason: ITMS-90338: Non-public API usage - The app references non-public symbols in GPS: _CCCryptorGCMOneshotEncrypt. 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.... This is just a regular app update, we didn't do any big changes and we don't use this function or anything related to CommonCrypto/Cryptography in the app. We tried to submit a Code Level Support request but always receive a Gateway Timeout. Has anyone came across a similiar experience and would be able to help?

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

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

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

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.