ITMS-90158

From appstore receive email with this issues: ITMS-90738: Invalid purpose string value - The “NSPhotoLibraryUsageDescription” value for the NSPhotoLibraryUsageDescription key isn’t allowed in “.....”. 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 “.....” bundle should contain a NSPhotoLibraryUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. ITMS-90738: Invalid purpose string value - The “NSCameraUsageDescription” value for the NSCameraUsageDescription key isn’t allowed in “....”. 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 “.....” bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. I

I get this error when trying to submit a beta build. App Store Connect Operation Error ERROR ITMS-90334: Invalid Code Signature Identifier. The identifier com.apple.WK in your code signature for app name watch must match its Bundle Identifier com.appname.watchkitapp I don't know of anything that has changed with the code signing since last successful submission, can't find com.apple.WK anywhere in my project and have tried submitting a previous version with no changes and get the same error. Anyone have any idea what I could be doing wrong?

issue: ITMS-90999: Invalid executable - The executable in “xxx.app” contains multiple segments with the executable permission bit set when it should only contain one. After you’ve corrected the issues, you can upload a new binary to App Store Connect. we use Xcode 14.2 and Xcode 14.3.1 both meet the same problem today(with previous uploaded code to archive and upload also with code 90999).How does it happen? And we do not meet the error code ITMS-90999 at last week.

We're trying to submit an App Clip with around 17mb, aiming to fit in the new size limit for digital invocations. The mention for the rules can be found in this article.. The relevant part is: If you make your App Clip available on devices running iOS 16.4 and later, your App Clip can be up to 50 MB in size if it meets the following conditions: The App Clip only supports digital invocations — for example, from your website or Spotlight search — and not from physical invocations but like App Clip Codes, QR codes, or NFC tags People use your App Clip in situations where a reliable internet connection is likely, for example, at home Your App Clip doesn’t support iOS versions prior to iOS 16.4 We have updated our App Clip target to have a minimum supported version to iOS 16.4 but when we push it to TestFlight we get an error like below: We identified one or more issues with a recent delivery for your app, (...) Please correct the following issues, then upload again. ITMS-90865: Thinned app clip size is t

So we checked the: Supports running without ios app installation, and it updated our app on the app store. Now we are seeing a lot of instances where our users have one version of the Watch app, and another of the iOS companion app. We have also been collecting a myriad of random crashes, and we can't help but wonder if it's due to these apps being out of sync. We'd like to roll back and test this theory by making the watch app and the iPhone apps dependent on each other again. However, after opting on Apple Connect to Remove from sale, and then Remove app, we cannot push a new version with the change. I get the following error:ERROR ITMS-90768: Invalid Bundle. The watch app '[app]' watch extension must have 'WKWatchOnly' or 'WKRunsIndependentlyOfCompanionApp' Info.plist keys set to 'true', since a version of this app that supports standalone watchOS devices is currently available on the App StoreDoes anyone know a way we can get back to having these apps dependent? Thanks.

We publish many apps using our CI/CD system that makes use of the App Store Connect API and iTMSTransporter. Since around 9:00am on 19 Oct 2023 (Melbourne/Australia time UTC+10), all our attempts to upload our .ipa files using iTMSTransporter began failing. The specific command line invocation is: /usr/local/itms/bin/iTMSTransporter -m upload -v eXtreme -f /path/to/Bundle.itmsp -jwt {jwt-here} The error is occurring in the midst of the upload with the error message: Apple's web service operation return value: [2023-10-20 09:35:09 AEDT] DBG-X: parameter Errors = [An error occurred while trying to call the requested method validateAssets. (1272)] [2023-10-20 09:35:09 AEDT] DBG-X: parameter RestartClient = false [2023-10-20 09:35:09 AEDT] DBG-X: parameter ErrorCode = 1272 [2023-10-20 09:35:09 AEDT] DBG-X: parameter ErrorMessage = An error occurred while trying to call the requested method validateAssets. (1272) [2023-10-20 09:35:09 AEDT] DBG-X: parameter Success = false [2023-10-20 09:35:09 AEDT]

We have an iOS In-House app that is not installing using the OTA method. The app is no longer able to be installed using the itms-services:// protocol. The last time I tried it was in November 2020 and it worked then. The uri looks like this itms-services://?action=download-manifest&url=https: //dl.dropbox.com/s/abcdef123/manifest.plist . Our Enterprise certificate and profiles are up to date and valid. I was able to install the app to an iphone using Xcode and an Ad-hoc deployment of the app. The dropbox links are all shared and accessible to anyone with the link. When I copy the itms-services uri to Safari on an iPhone I get the popup ... Open this page in iTunes? with the options Cancel and Open. When I click Open the popup goes away but then nothing else happens. The app does not install. I connected to XCode Console to view the log messages for the device while clicking Open on the popup and the only message that stood out to me was .. Process: itunesstored Message: Network

We have an app that was provided to us by a third-party developer. I do not have access to the source code or the xcodeproj file for this app. I have re-signed the app, using the iResign utility, with a distribution certificate and an App Store provisioning profile that I created in our developer account. I extracted the entitlements.plist file from the app using codesign, and updated it, replacing the third-party developer's Team ID and bundle ID, and assigned it an bundle ID that is from an App ID that I also created in the developer portal. Our team ID is 12A345BCDE, and the bundle ID value is com.myiosapp. The iResign process is successful. I have the Change ID box checked on iResign, with the new bundle ID value provided in the field.When I submit the app using Application Loader, I get multiple instances of this error:ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that arenot supported on iOS. Specifically, value '12A3

I've been trying to upload a test build using Xcode 13 to TestFlight but keep getting the following error after build is uploaded successfully: ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: /Volumes/data01/app_data/awf/SWImportWorker-pv50p00ce-swpr152.cse.apple.com-400203/ff08-SoftwareImportWorker-PV_.0/VWBGHTOVAUPPUUZ65REE64UUN4/eqbyjijjamvooymq/exddmvmbsqjsrxwj/Payload/[App Name].app/[App Name]. Remove the instructions from the binaries, rebuild and resubmit. What does this error mean? What are those prohibited instructions? Where to fine them in the app binary? Any guidance is appreciated. Thanks.