“ITMS-90338”

Hello. Please let me preface my question with this: I am new to IOS development, XCode and Mac computers, in general. So, apologies if my question sounds uniformed. I have built a prototype game, which I would like to put on the App Store, so that my friends and partners can test. I only want this available via the internet, so that they can access the app and test, internally. It is not ready to go into production. I build the app in Unity and ported to Xcode. I build the applications Archive and follow the process to upload it. I receive no errors. But, after I upload the application, and it finishes processing, the status (under iOS Builds) is Invalid Binary. I also received an email that said: ITMS-90562: Invalid Bundle - The app cannot be processed because options not allowed to be embedded in bitcode are detected in the submission. It is likely that you are not building the app with the toolchain provided in Xcode. Rebuild your entire app with the latest GM Xcode and submit the app again. How c

Hi all, I am facing an error when I try to upload my resigned .ipa file to the App Store. Basically what we want to achieve is that we get an unsigned .ipa file from an external company (we don't own the source code for this app), and we want to distribute that with our company developer account. (as a private app) We already have a Developer Account, I registered the App, Bundle Id, created certificate, App Store provisioning profile etc. And with these I resigned the .ipa file. But when I try to upload to the App Store (via altool command) I have the following error: parameter ErrorMessage = ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value '***.com.company.myappname' for key 'application-identifier' in 'Payload/FSARN.app/Frameworks/FMDB.framework/FMDB' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle ide

Is it possible to set up Xcode Cloud so it distributes the app to different bundle id? (for example, mock, test and release environment) Right at the moment we are only limited to deploy TestFlight for the bundle ID that configured Xcode Cloud? I would really like to be able automate several different build with different bundle id's... When i try to archive using Xcode Cloud to a different bundle id that the one configuring Xcode Cloud i get the following errors: ITMS-90054: This bundle is is invalid. ITMS-90345: Metadata.Info.plist Mismatch. When I archive manually it works perfectly fine.

Our app uploads successfully, but then I get the following message in an email from App Store Connect about an Invalid Code Signing Entitlements: ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value 'BFZC26JH2W.humansarehuman.blue2factor.macosbackground' for key 'com.apple.application-identifier' in 'Blue2Factor.app/Contents/Library/LoginItems/Blue2FactorBackground.app/Contents/MacOS/Blue2FactorBackground' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . The value for the key mentioned, BFZC26JH2W.humansarehuman.blue2factor.macosbackground, IS our TEAMID, followed by a dot, followed by the bundle identifier. The bundle is a target in our project, though it is not only target, and it is not the bundle ID that is identified as the BundleID on the App Store Connect - App Information page under the Gener

Hi, community, when I build my project I have the same reject from App Store: ITMS-90430: Invalid Swift Support - The file libswiftAVFoundation.dylib doesn’t have a signing ID. Sign the file, rebuild your app using the current public (GM) version of Xcode, and resubmit it I follow a procedure before the build, but this works one time on X times... cleanup pods - cd ios & pod deintegrate & pod update cleanup Xcode derived data - rm -rf ~/Library/Developer/Xcode/DerivedData/* clean build folder Product->Clean Build Folder in Xcode Specs below: OSX: big sure 11.4 XCode: 13.2.1 Libs: native-base: ^2.15.2, npm: ^7.10.0, react: 17.0.1, react-native: 0.64.1, react-redux: ^7.2.4, redux: ^4.1.0, rxjs: ^6.6.7, @types/react-native: ^0.64.0, typescript: ^3.8.3 This bothers me ... I waste hours on builds. Regards AA

I have developed MacOS App and tried to make installer which has postinstall by productbuild. productbuild --component App/App.app /Applications --scripts ./Scripts --sign 3rd Party Mac Developer Installer: MyCompany (******) App.pkg Scripts directory has postinstall. -rwxr-xr-x@ 1 name staff 171 1 7 11:36 postinstall* I can install App.app under /Applications. But postinstall is not called. App.pkg is validated by Transporter. I tried to use pkgbuild. pkgbuild --root ./App --identifier com.mycompany.App --version 1.0 --install-location /Applications --scripts ./Scripts --ownership preserve App.pkg productbuild --synthesize --package App.pkg Distribution.xml productbuild --distribution Distribution.xml --sign 3rd Party Mac Developer Installer: MyCompany (******) --package-path . AppInstaller.pkg This dose work well, postinstall is called. But AppInstaller.pkg is not validated by Transporter with following errors. What should I do ??? ERROR ITMS-90230: Invalid product archive metadata. Error in keyPat

I want to upload a MacOS App to App Store Connect and have it be available to test in TestFlight. I have already managed to sign the application as needed, as I can upload builds. The problem is, that they get marked as Not Available for Testing. At first App Store Connect notified me of this issue: ITMS-90889: 'Cannot be used with TestFlight because the bundle at “RougeLike.app” is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight.' I added a provisioning profile to the app bundle at Contents/embedded.provisionprofile. Now I don't get this notification anymore, but the app still is marked as Not Available for Testing. Does anybody know how to solve that?

Hi, I was wondering could we tell the difference if a user is redeemed among Subscription Offer Codes and the others two types of Offers (Introductory Offers, Promotional Offers) when receiving shouldAddStorePayment callback? I didn't see there is a SKProductDiscount.Type for it. https://developer.apple.com/documentation/storekit/skproductdiscount/type When a user redeem offer code by typing manually in AppStore App or via itms-apps://buy.itunes.apple.com/WebObjects/MZFinance.woa/wa/freeProductCodeWizard?code=YOUR_CODE URL , I think we could expect that there should be a paymentQueue(_:shouldAddStorePayment:for:) to inform SKPaymentTransactionObserver about the event according to the document. https://developer.apple.com/documentation/storekit/skpaymenttransactionobserver/2877502-paymentqueue If your app is not yet installed when the user starts the in-app purchase in the App Store, the user gets a notification when the app installation is complete. This method is called when the user taps the notifi

I got next error: ERROR ITMS-90683: Missing Purpose String in Info.plist. Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSHealthShareUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy). But it's just a new build of a project and Info.plist seems to be ok (nobody has changed it):

Hi, I am unable to upload my app with mac book pro (13 inch ,M1) , Xcode 13.2.1 (13C100), swift 5, and cocoapods-1.10.1 version, receiving following mail from App Store connect after 10 mins of upload to TestFlight or AppStore. Error : We identified one or more issues with a recent delivery for your app, MyApp 1.4.6 (89). Please correct the following issues, then upload again. ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswift_Concurrency.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftPhotos.dylib, libswiftMediaPlayer.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/MyApp.app

I'm not sure what type of provisioning profile I need to create for my Mac App to allow TestFlight. I am archiving the app through Xcode and allowing it to control the provisioning but it still does not work.