“ITMS-90338”

I have the problem after I upload build to App Store Connect. I always get error ITMS-90129: The bundle uses a bundle name or display name that is already taken.. when I set CFBundleDisplayName and CFBundleName to be Companion but if I set to others such as ECHO then it can be uploaded without error. I contact to support via email and case number is 102554754170 and Bobby from developer support suggested me. The problem was that the Product Name was different than the Display Name.” I replied email that I tried it as below. Target Name = Companion, Product Name = $(TARGET_NAME), CFBundleDisplayName = $(PRODUCT_NAME), CFBundleName = $(PRODUCT_NAME) Target Name = Companion, Product Name = Companion, CFBundleDisplayName = Companion, CFBundleName = Companion I still get error but if I change CFBundleDisplayName and CFBundleName to be other app name such as ECHO, Facebook then it can be uploaded successfully. I'm not sure if there is something with Companion on validation process. Then he suggest me to co

Hello guys i have a problem. I have one template package. and I publish many applications using this package. i change only names and colors. my other other project working fine , there is no problem. But I get this error on new one of them. My PrivacyInfo like this and my copy bundle resources like this i cant handle this problem . please help

After submitting our binary for review, we are receiving the Invalid Binary error, which appears to be related to the absence of privacy manifests for our third-party SDKs. Here is the part of an Appstore Connect email response (it's a part of a long email, containing such errors for 18 SDKs): ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/AppAuth.framework/AppAuth”, which includes AppAuth, 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. Our application is built using Xamarin, and there are currently no available updates for the libraries that include the required manifests. Instead, we have a single consolidated privacy manifest that contains data for all the SDKs used

ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. If your app uses APNs, make sure the App ID is enabled for push notifications in Certificates, Identifiers & Profiles, sign the app with a distribution provisioning profile that includes the APS Environment Entitlement, and upload a new build to ensure that push notifications function as intended. For details, visit: https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns.

We have a macOS app that has a Photos Extension, which shares documents with the app via an app group container. Historically we used to have an iOS-style group identifier (group.${TeamIdentifier}${groupName}), because we were lead by the web interface in the developer portal to believe this to be the right way to name groups. Later with the first macOS 15 betas last year there was a bug with the operating system warning users, our app would access data from different apps, but it was our own app group container directory. Therefore we added a macOS-style group identifier (${TeamIdentifier}${groupName}) and wrote a migration of documents to the new group container directory. So basically we need to have access to these two app group containers for the foreseeable future. Now with the introduction of iOS-style group identifiers for macOS, Xcode Cloud no longer archives our app for TestFlight or AppStore, because it complains: ITMS-90286: Invalid code signing entitlements - Your application bundle’s si

Hi, our team received this message ITMS-90725: SDK version issue - This app was built with the iOS 17.0 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. We still have a requirement to support iOS 12.5.7 for our users. If I change to build SDK iOS18 using Xcode 16 or later, will my app submission be rejected during review process? (since I specified my minimum iOS version to be 12)

Flutter iOS App. Previous version submitted passed. Only change the version and some text, submit has 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. the release steps: flutter clean; flutter pub get; flutter build ios --release; xcode - clean build folder; archive; distribute app Searched online and tried many suggestions, none works.

I'm trying to use Transporter to upload my .ipa file to the Apple Store and make it available on TestFlight. I'm generating the .ipa with the command eas build -p ios --profile production. However, I'm receiving the ITMS-90426 error in my email. I've seen many suggested solutions for this issue, but most of them involve using Xcode. The problem is, I don't use Xcode. I only use Transporter on my Mac to upload the app, and I develop on a Windows environment. Could you please guide me on how to generate the required files using Expo/EAS to avoid this issue?