ITMS-90158

When building xcode project of an application with login item included/embedded (another target), locally it works without problems. But when building on xcode cloud, we are getting the error: ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “XXX.***.***” value for the com.apple.application-identifier key in “Path_to_login_Item” isn’t supported. This value should be a string that starts with your Team ID, followed by a dot (“.”), followed by the bundle ID. If there are no capabilities added to the login item's target (only com.apple.security.inherit and App Sandbox), the project builds without errors. But our login item needs to access a database in app group container and sync its data with iCloud, so after adding iCloud and App Group entitlements, building on xcode cloud fails with the error written above. Locally it builds and runs without problems. So, what should be done to fix

Hi all, I have repeatedly the issue that a certain .strings file in my app's bundle has the extended files attribute com.apple.quarantine set. Consequently the submission fails with the following mail notification: We noticed one or more issues with a recent delivery for the following app: [...] ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute, such as “abcdef.strings”. This attribute isn’t permitted in macOS apps distributed on TestFlight or the App Store. Please remove the attribute from all files within your app and upload again. I'm able to resubmit the bundle after cleaning the file attribute via xattr -d -r com.apple.quarantine..., but the funny thing is it happens again and again - on a .strings file which hasn't been downloaded (but manually created), shouldn't be under Gatekeeper's quarantine, and wasn't edited in the meantime. Is anybody else observing the same issue with macOS 15.4.1, Xcode 16.3? Greetings,

Hello, At my company, we're trying to run an App Store A/B test on alternate app icons. However, the App Store is rejecting the binary when we upload it (see email below). We're hoping someone out there knows the solution to this issue. Background Currently, our app is built with one target from amongst several different schemes. These schemes are used for various versions, including developer debug builds, TestFlight builds, App Store builds, and others. Each scheme has its own distinct app icon specified in Xcode, as shown in the image below: In our project, we've added the alternate app icons for the two App Store treatments as recommended according to Apple's documentation (we named them AppIcon-T1 and AppIcon-T2). These are located inside our Images.xcassets asset catalog. Each alternate app icon's properties are configured as: iOS: Single Size macOS: None watchOS: None Appearances: None Gamut: Any The Problem After making the changes above, creating an App Store build succeeds as usual. However, every t

Getting the following error from AppStore Connect ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. Refer to QA1623 for additional information: https://developer.apple.com/library/ios/#qa/qa1623/_index.html We haven't changed the UIRequiredDeviceCapabilities value since our last production build. I've verified that by downloading the prior release and comparing the bundled info plist - the value we had arm64, remains the same. Is anyone else seeing this issue all of a sudden?

Hi, We've created a new version of our macOS version of our app, but when I now try to upload the generated .pkg to App Store Connect via Xcode or Transporter we get this error message: ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “AppIDPrefix.my.bundle.name” value for the com.apple.application-identifier key in “my.bundlename.pkg/Payload/appname.app/Contents/MacOS/appname” isn’t supported. This value should be a string that starts with your Team ID, followed by a dot (“.”), followed by the bundle ID. Setting the code signing to automatic or does not make a difference. Our app has a different App ID Prefix as our Team ID and when I try to upload the app to App Store Connect I get this error message, does anyone know how we can fix this issue? We used to be able to upload the apps without issues.

Hello, I am normally a windows programmer, but I am trying to get my PySide/Qt app into the app store. I'm almost there, I just have a couple of questions about the signing process. I have two laptops, one intel silicon, one mac silicon. I created 2 CSR's, one on each laptop and used them to generate 2 Mac Installer Distribution certificates and 2 Mac App Distribution certificates. When it came to downloading the provisioning profile, I selected one Mac App Distrbution Certificate on the interface at developer.apple.com, saved it and then downloaded to the appropriate laptop. I then switched the provisioning profile to the other Mac App Distribution Certificate and downloaded it to the other laptop. I then built the app and uploaded everything using xcrun altool. On the intel machine only(which has the first provisioning profile) I successfully uploaded the package but I get an email identifying lots of similar errors of the type (Lets call it error1): ITMS-90284: Invalid Code Signing - The executabl

Hi When attempting to upload a React Native app (version 0.77) we encountered the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. If to check ipa folder we can see that content includes only 2 folders: Payload Symbols Could you please tell us why it does not include Swift Support folder? We tried to use XCode - 16.2 and 16.3 Thank you

I received the following message in my email: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. But I don't know how to find the problem. How should I find and solve the problem？

Please correct the following issues and upload a new binary to App Store Connect. ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/FirebaseCoreDiagnostics.framework/FirebaseCoreDiagnostics”, which includes FirebaseCoreDiagnostics, an SDK that was identified in the documentation as a commonly used third-party SDK. If a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/FBLPromises.framework/FBLPromises”, which includes FBLPromises, an SDK that was identified in the documentation as a commonly used thir

Hello All, I am hoping someone has a solution we are encountering. We recently upgraded to XCode 16.3 this week, and were putting together the next test build to push to TestFlight. However, the AppStore is rejecting the app with the following message. ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols] We have never had this before and the problem is, there is no path named _Symbols in our IPA. Doing some searching online I have seen people report the same problem when build using Flutter or React, but we are using plain vanilla Swift and Native iOS. We also have not added anything significantly new to our project since our last release a couple weeks ago. Any suggestion on how to fix this would be greatly apprecaited. Sincerely, Stan R. - CaringBridge

When i try to publish the app. I am getting this Warning. ITMS-90725: SDK version issue - This app was built with the iOS 17.2 SDK. Starting April 24, 2025, all iOS and iPadOS apps must be built with the iOS 18 SDK or later, included in Xcode 16 or later, in order to be uploaded to App Store Connect or submitted for distribution. I have few clarification on this. How much time do we generally have to publish the apps. If i have a App that is successfully reviewed and certified from apple team and I have Chosen to Manually release this Version. Is it possible to Publish the App built using SDK 17.x After 24th April 2024. If the app is reviewed and certified before the April 24th timeline. If so, how long can i hold the published & certified app and publish. Without the need to rebuild and re-apply for certification.