ITMS-90158

There is an issue with Ad-Hoc signing of dynamic libraries built either through a Swift Package, or through an Xcode target with a non-standard Bundle ID (i.e. one not using reverse DNS format), resulting in the ITMS-90334 error message. We'd appreciate getting reports of this filed through Feedback Assistant, and then posting the FB number here so that I can follow-up on the reports internally. Even if the following workaround information is helpful to you, we'd still appreciate getting the Feedback reports. The best practice for Swift packages is to not explicitly specify the LibraryType in the Product. By not specifying this value, you let Xcode decide the best linkage type for your app's usage of the package. If you have a package that is explicitly marked as dynamic, removing the library type means Xcode will link the package statically if the package is only imported by one target, which will avoid the issue. If the package is imported by more than one target, Xcode will choose dynamic linkage

Me too, but a simple app using Swift Playgrounds on iPad. I sent a message to support about this describing what I was doing, and a copy of the error and got the response: “We're unable to determine the nature of your request. Please reply to this email with clarification”. This was the error I get back in email: ITMS-90334: Invalid Code Signature Identifier - The identifier 'Johnboxgame-numbers_and_letters_that_forums_thinks_are_offensive' in your code signature for 'Johnboxgame' must match its Bundle Identifier 'Johnboxgame' WIth the iPad app there’s not really much I can control as far as what goes in the bundle, and it’s worked in the past.

Okay, it turns out there is an issue with this strategy. We got ITMS-90078: Missing Push Notification Entitlement error after uploading the IPA to App Store. Very annoying.

For me it was related to static vs dynamic builds, detailed it here: https://stackoverflow.com/questions/72291080/itms-90334-invalid-code-signature-identifier-when-building-via-xcode-cloud/73653319#73653319

Any Update? I also had an issue related to Invalid Swift Support. This was a minor change from a version that passed review a few days earlier, and now the binary is invalid. Our issue was: ITMS-90433: Invalid Swift Support - The file libswift_Concurrency.dylib doesn't have the correct code signature. The previous build was Xcode 13.2.1, and we can't build on Xcode 14 due to a dependency that needs to be updated.

I'm seeing this issue in one of the apps I work on. I saw it first in crashlogs (Bugsnag) in July but last 2 weeks the number of reported crashes skyrocketed. The app doesn't explicitly use the SKStoreProductViewController. It uses UIApplication.shared.open(itms-apps://apps.apple.com/app/appid) and the SKStoreReviewController.requestReview(), I'm not sure which one of these uses the SKStoreProductViewController. What is very odd, the other 2 apps that use the same way to show the other product app pages don't have this crash in their logs. Edit: I saw somebody mentioned the issue could be related to AdMob. This app also uses AdMob, the other 2 apps don't use AdMob.

Seeing this crash too. I believe it's been around since the first release of M1 Macs. Confirming also that workaround of using itms-apps://apple.com/app/id***** works.

Still here: (React native) ITMS-90338: Non-public API usage - The app references non-public selectors in App: _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, onSuccess:. 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.