ITMS-90158

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.

I'm an indie developer. My latest minor update for my game which has been on the Mac App Store for 13 years and which has spent time at #1 on the download charts just started getting rejected for the following reason: Guideline 2.5.2 - Performance - Software Requirements The app installed or launched executable code. Specifically, the app uses the itms-services URL scheme to install an app. However my app is certainly not installing any apps and to the best of my knowlege it is not using any itms/itunes/etc. type URLs in any way, so I can't figure out what would be triggering this claim. Inquiries as to what app I am supposedly installing or what URL I am supposedly using have yielded 'no further information can be provided'. Has anyone run into something similar? Any ideas on obscure scenarios that could trigger this particular rejection? Or any advice on what one should do in my situation? I feel a bit stuck. Has anyone had luck with the appeal process for this sort of thing (to at least g

Hello, I need help because I have not succeeded to fix the following issues: ITMS-90738: Invalid purpose string value - The “NSLocationAlwaysAndWhenInUseUsageDescription” value for the NSLocationAlwaysAndWhenInUseUsageDescription key isn’t allowed in “SuperNewsV2UIKit.app”. Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “SuperNewsV2UIKit.app” bundle should contain a NSLocationAlwaysAndWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources. ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “SuperN

But this one doesn't specify where the problem is, such as the use of a private api or if it's using a key that shouldn't be used, or anything else. Now we need to find out what's causing this problem, can you give us some direction or ideas?

While uploading the application into the TestFlight the following error received, ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. After sometimes generate same configuration the application successfully submitted on the TestFlight. We are using Xcode 15.3

Hello,We contacted Apple Developer Support due to an automatic message we receive when trying to publish a new version of our appDear Developer, We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in Idealys: applicationWillTerminate, ddSetLogLevel:, localTarget, newSocketQueueForConnectionFromAddress:onSocket:, setOrientation:animated:, socket:didConnectToHost:port:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidSecure:, terminateWithSuccess, webSocket:didReceiveMessage:, webSocketDidOpen: 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

Hi there, I uploaded an update bundle for the posted app, but I got a rejection message. ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols] The XCode version I'm using is 16.2, and I've been trying to find a route using Run Script and Finder, but I don't know what the hell it is about. Does anybody know what could cause this issue? Any help would be appreciated. Thanks.

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

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

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, I recently updated my app, and in the Transporter app it said that the processing failed. This is the email I recieved: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols] I couldn't find anything related to this in XCode or anywhere else on the internet. What did I do wrong? For context, I am developing using Expo and React Native.

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.