“ITMS-90338”

Hello everyone, I have been developing a game in UE4 and I would like to send my build to TestFlight. I'm working on a windows machine and remote build my project on a updated Mac book pro with Monterey and Xcode 13.1 I have no problem generating the development build and the shipping build on the windows side. However when I try to upload the .ipa using transporter I get this error message that suggest that the SDK used to compile is not the right one. ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 13.2 SDK. All iOS apps submitted to the App Store must be built with the iOS 14 SDK or later, included in Xcode 12 or later. I should add that, in the past, I have been able to upload the game on iTunes connect. Any help would be greatly appreciate Best

I have successfully built, signed, and archived my app! However, when I try to send it to App Store Connect (I've tried using Transporter and Fastlane), I get this error: ERROR ITMS-90161: Invalid Provisioning Profile. The provisioning profile included in the bundle com.myapp [Payload/My App.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal. I am indeed using a distribution provisioning profile, and I have the codesigning certificate on the machines doing the building. I've tried deleting both from all machines, then re-downloading them from Apple Developer, but that doesn't seem to have fixed the issue.

Hello everyone i have an error when I'm trying to upload an update for my app. This is the error code: Package Summary: 1 package(s) were not uploaded because they had problems: /var/folders/0n/dd16qmb94g7g26jws4t7hjjh0000gn/T/CEC762F0-0533-4764-AFD9-761840FEEF28/1589750783-1.2-1.2-1.itmsp - Error Messages: ERROR ITMS-90161: Invalid Provisioning Profile. The provisioning profile included in the bundle [Payload/BBPlayer.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal. I can't figure out how to fix this. i have searched all over the net and can't get it to work. I't would be nice with inputs and fixes. So if you have an ide just send it will make my day !

I have App Store Connect issues, after when I transferred application another account. ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['oldID.iosapp'] and the new version of software being submitted has an application-identifier of ['newID.iosapp']. This will result in a loss of keychain access. development team changed and what can I do ?

I use UE4 to build a ipa and install it by itms-services. When I use Ad-Hoc profile (Develop account) to release ipa , it can be install successfully. But there had some error when I use In-House profile(Enterprise account) to release it. Error Message: Unable To Install NGR Console Log: Oct 20 11:43:41 DSJ-iphone runningboardd(RunningBoard)[32] : Invalidating assertion 32-16661-47469 (target:system) from originator [daemon:16661] Oct 20 11:43:41 DSJ-iphone installd(MobileSystemServices)[16661] : 0x16d22f000 -[MIClientConnection updatePlaceholderMetadataForApp:installType:failureReason:underlyingError:failureSource:completion:]: Update placeholder metadata requested by client installcoordinationd (pid 16544 (501/501)) for app com.NGR.publishshipping installType = 7 failureReason = 1 underlyingError = Error Domain=MIInstallerErrorDomain Code=5 Could not extract archive UserInfo={NSUnderlyingError=0x103014420 {Error Domain=NSPOSIXErrorDomain Code=0 Undefined error: 0}, LegacyErrorString=PackageExtracti

I got this note from the App Store with my last update: Dear Developer, We identified one or more issues with a recent delivery for your app, “Bills & Periodicals” 1.2 (20). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90863: Apple silicon Macs support issue - The app uses symbols that are not present on Mac: /usr/lib/swift/libswiftFoundation.dylib _$s10Foundation24FloatingPointFormatStyleV8CurrencyV4code6localeAEyx_GSS_AA6LocaleVtcfC _$s10Foundation24FloatingPointFormatStyleV8CurrencyVyx_GAA0dE0AAMc After you’ve corrected the issues, you can upload a new binary to App Store Connect. Best regards, The App Store Team I don't know how to use the information provided to identify the problem. Can anyone help?

I recently upgraded my project's deployment target version to iOS 12.0 and started getting warnings saying: ITMS-90747: Architecture incompatible with MinimumOSVersion. The app bundle at 'MyProject.app/PlugIns/StickerPack.appex' specifies a MinimumOSVersion of '12.0' but contains a 32-bit architecture that is unsupported on iOS 12 and later. I did some research and found a few people having the same issue, one common suggestion is to lower the project's deployment target version, this isn't possible for the main target because I have a few libraries that have minimum OS version requirements. So I wonder what should be the right way to fix this, so far I can think of two solutions: The Message Extension target's Architectures is currently $(ARCHS_STANDARD) which translates to (arm64, armv7), so I can change it explicitly to arm64 only, or add armv7 to Excluded Architectures which sounds better. Change the iOS Deployment Target to some version lower and do this only for the Message Extension target. I'

Hi! My app has App Icon set up and it was working perfectly up until about 3 weeks ago. Now I see blank logo on the screen and cannot Submit for Review new builds, because it shows the following errors: ERROR ITMS-90713: Missing info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle. ERROR ITMS-90704: Missing App icon. An app icon measuring 1024 by 1024 pixels in PNG format must be included in the Asset Catalog of apps built for IOS... But I have : appIcon set up for all sizes showing no errors App Icon source in Target -> General is chosen as AppIcon 'CFBundleIconName' - 'AppIcon' in info.plist Successfully uploaded app version to App store around 3 weeks ago. I suspect it may have started after I switched to the new build system (which made me remove info.plist from Copy Bundle Resources in Build Phases). Looks like a similar issue to that one https://developer.apple.com/forums/thread/682648 Will be grateful for any help! Xcode Version 13.0 (13A233

We were able to validate and upload a mac arcade build to ASC, but when submitting it for review we got this message from Apple: ITMS-90812: Arcade static library missing or not correctly linked. The app does not link against the library performing the Arcade subscription check. I've never seen this error message before. For context, we recently upgraded to Unity 2020 to support Apple silicon. The build launches and runs without any issues so not sure how to address the issue. FYI 'Mac Store App Validation' is checked in the build settings. Any help would be appreciated!

Hi, I have xcode 13 and when trying to publish with this version for the first time I get this error in validation. ITMS-90496: Invalid Executable - The executable 'xxxxx WatchKit App.app/PlugIns/xxxx WatchKit Extension.appex/xxx WatchKit Extension' does not contain bitcode. How could i fix it? thanks!!!

Hi, When packaging an application using JDK 17 and the latest version of jpackage I get the below error when uploading to the App Store. All test prior to uploading complete just fine. I think it might be realated to the structure of the .app folder but not sure, any ideas would be helpful ITMS-90238: Invalid Signature - The main app bundle Test at path Test.app has following signing error(s): a sealed resource is missing or invalid. Refer to the Code Signing ... and ITMS-90296: App sandbox not enabled - The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[Test.app/Contents/MacOS/Test]] The app verifies in Transporter just fine and codesign as well. codesign --verify --verbose=4 'Test.app' Test.app: valid on disk Test.app: satisfies its Designated Requirement Also entitlements seems to be fine. codesign -d --entitlements :- ./Test.app/Contents/MacOS/Test Executable=/Users/ryan/flat/Test.app/C