“ITMS-90338”

Hello, after submitting my pkg-Packet I got this Email: Dear Developer, We identified one or more issues with a recent delivery for your app, Mobile Inear Mix for Mac 1.0 (1.0.9). Please correct the following issues, then upload again. ITMS-90238: Invalid Signature - The main app bundle Mobile Inear Mix for Mac at path BroadcastServer.app has following signing error(s): --prepared:/Volumes/data01/app_data/awf/mz_2656175418978928526dir/mz_12035317582602409589dir/com.mobileinear.BroadcastServer.pkg/Payload/BroadcastServer.app/Contents/PlugIns/mediaservice/libqavfmediaplayer.dylib --validated:/Volumes/data01/app_data/awf/mz_2656175418978928526dir/mz_12035317582602409589dir/com.mobileinear.BroadcastServer.pkg/Payload/BroadcastServer.app/Contents/PlugIns/mediaservice/libqavfmediaplayer.dylib --prepared:/Volumes/data01/app_data/awf/mz_2656175418978928526dir/mz_12035317582602409589dir/com.mobileinear.BroadcastServer.pkg/Payload/BroadcastServer.app/Contents/PlugIns/platforminputcontexts/libqtvirtualkeyboardp

Can anyone explain more about what this App Store Connect Upload error could be? As far as I can tell this intent is only in a single intent extension, but I'm willing to learn how to better investigate. ERROR ITMS-90674: Intents Extension Issue. The intent CopyToGalleryIntent is in multiple intents extensions, but it can only be in one.

Hello I've released a production IPA to upload to TestFlight for internal testing. When we're trying to upload the IPA to TestFlight we're getting an ITMS-90165 error. while it was working fine a couple of days back Can anyone help me find out what this error means? Thank you.

Hello, I'm having troubles trying to upload an iOS app to the AppStore. When I export the app and try to upload it to TestFlight receiving the following error (ERROR ITMS-90075): This bundle is invalid. The application-identifier entitlement is missing; it should contain your 10-character Apple Developer ID, followed by a dot, followed by your bundle identifier. I've been using manual exporting using Xcode 12.4 and fastlane and both methods fail. In the Entitlements.plist file it appears the key application-identifier pointing to the right bundle and also in the Provisioning profile is set the right app id. There is no errors in the IPA Preview prior uploading. What else can I be missing? Thank you.

We've started hitting this limitation when submitting builds using Xcode Cloud. ITMS-90382: Upload limit reached - The upload limit for your application has been reached. Please wait 1 day and try again. We generate TestFlight builds for every PR (builds from PR get sent to QA & devs) & for every merge (builds get sent to everybody in the team). Is there any way to know what's the limit so we can try to work around it? Edit: I've just checked, and TestFlight only reports 19 builds that are expiring in 90 days (aka were uploaded within the last 24h). Is the limit that low?

Hi, I am facing a problem with Xcode 12.3, swift 5, and cocoapods-1.10.1 version when I want to publish my archive on Appstore Connect, everything goes well, but once the application sent I receive an e-mail from App Store Connect with the following error : ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftContacts.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftMediaPlayer.dylib, libswiftCloudKit.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/WoWonder.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and

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.

We have transferred our app from App Store Connect account to another. Transfer process was smooth and we we were able to move our app to new App Store account While uploading the new build for our app using the new account we received the below email. Can someone shed some lights on this and how can we make user to not to logout. ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['94B63VZT32.com.prasthana.tenmates'] and the new version of software being submitted has an application-identifier of ['G3M3U47GBZ.com.prasthana.tenmates']. This will result in a loss of keychain access.

My build using getentropy() was rejected. Although this is clearly recommended by documentation. https://support.apple.com/guide/security/random-number-generation-seca0c73a75b/web ITMS-90338: Non-public API usage - The app references non-public symbols in ***: _getentropy. 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. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

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?

I'm uploading a new biuild of my iOS/Apple Watch app to App Store, but it's failing withERROR ITMS-90081: This bundle is invaled. Applications built for more than one architecture require an iOS Deployment Target of 3.0 or laterWhich just doesn't make sense. The iPhone component is built for Deployment Target 11.0.I haven't messed with these settings for the past 10 uploads, but I have just ypgraded to Xcode 10 (from 9)What's occurring?

When I submit my code to TestFlight, I am getting an error as ERROR ITMS-90535: Unexpected CFBundleExecutable Key. The bundle at..... does not contain a bundle executable. If this is intentional, please consider removing the CFBundleExecutable Key from its info.plist and using a CFBundlePackageType of BNDL. If this is a third party....I have tried locating the info.plist file using xcode, but I do not see what field I need to change in order to fix this problem. I see that this is a common error code in all forums, but none of the sites I have seen, have a clear procedure. Please help!

When I try to create a TestFlight build of my app using Xcode Cloud, I get a couple of ITMS-90334 errors and the build fails. The error messages look like: ITMS-90334: Invalid Code Signature Identifier - The identifier 'MySwiftPackage-55554944e95A2da4fe9e3357b44de57c3ba890e8' in your code signature for 'MySwiftPackage_-658550CFFF128C8B_PackageProduct' must match its Bundle Identifier 'MySwiftPackage' Where MySwiftPackage is a Swift Package which is used by a framework as well as the application. The dependencies look like this: MyApp + MyFramework + MySwiftPackage + MySwiftPackage MyApp is a macOS app MyFramework is a mixed Swift and Objective-C framework MyApp is also mixed Swift and Objective-C When I run an archive build on my local Mac and upload the build to App Store Connect to be used as a TestFlight build, everything seams to be fine and the build is accepted I found some discussions on ITMS-90334 but not related to using Swift Packages and Frameworks Any ideas what might be

After using iOS16's new feature AppIntents, AppStore review is failed: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. I tried all methods in internet, but they all not work. Such as: I'm using the public version of Xcode I'm not using Ad hoc cert or .pp file I tried archive manually without using fastlane I tried change the Always Embed Swift Standard Libraries The only changes is iOS16's AppIntents. Before i use AppIntent, it works fine. After i use AppIntent, it failed. Only one commit between 2 .ipa. Can anyone help me? Many thanks.