“ITMS-90338”

After uploading a new iOS build, we received an error message via email from Apple stating: ITMS-90013: Corrupt Image File - The image file AppIcon60x60 2x.png appears to be corrupt. Strangely, we don't have any image file with that name in our project. It seems to be a build processing error on Apple's side. While I've seen similar issues reported for Apple TV in the past, this is happening with our iOS build. Has anyone discovered a workaround? I've uploaded another app build and haven't encountered any errors.

Hi, I am receiving the above error after trying to upload it to the App Store. I would know what to do IF Xcode would provide WHICH file is corrupt. The error reads: ITMS-90013: Corrupt Image File - The image file $[IconName] appears to be corrupt. Again, I would know what to do if I had more information about which file(s) to fix. Could anyone FROM APPLE help me or give me a hint? Thanks, Dan Uff

I added Privacy manifest for my app and submit it to review and apple reject my app with what comment ITMS-91054: Invalid API category declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SmartlookAnalytics.framework/SmartlookAnalytics” file contains “Disk Space” as the value for a NSPrivacyAccessedAPIType key, which is invalid. Values for NSPrivacyAccessedAPIType keys in any privacy manifest must be valid API categories. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api. i look at the package manifest and all looks fine (attached image). Maybe somebody saw that issue - and may tell me how can i fix it.

I have an iPad app on the App Store, and since recently every time I upload a new build to App Store Connect I receive an automated email with the following warning. ITMS-90984: Apple Vision Pro support issue - The details associated with your Apple Developer Program membership indicate that you’re not eligible to publish apps on the App Store for Apple Vision Pro. For more information, contact us: https://developer.apple.com/contact. At the present, my app does not target visionOS API specifically, but I have checked the checkbox for availability on Apple Vision Pro. According to the warning, something makes me not able to distribute apps for Vision Pro, but lacking any details I am not sure how I can solve this issue. What specifically about my account makes me ineligible to distribute apps for Apple Vision Pro and triggers this warning? I have contacted support at the provided URL, but they were unable to help me and redirected me to post in Developer Forums.

Hi everyone, I wanted to ask if anybody knows what the current status is about the declaration of required reasons APIs. Before May 1, when I uploaded a new build to the App Store Connect and added it to a group with external testers, I got a notification by email like the following: ITMS-91053: Missing API declaration - Your app’s code in the [...] file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryDiskSpace. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. In an article published by Apple (https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api) it is even statet that that after May 1, apps that do not comply are not accepted by the App Store Connect. According to

Hi everyone, I've been trying for a few days and still getting the same errors..so any help would be appreciated!! I've got the app to pass the Validation in XCode Organizer, but after I uploaded to Apple Store Connect through the Organizer, I'd get an email with errors, ITMS-90238: Invalid Signature, mentioning a long list of plugins, and then ITMS-90296: App sandbox not enabled. I'm not sure how to investigate these problems, so I've been just blindly trying everything. I've added the Sandbox capability in Xcode and have the entry in the entitlement file. The app even shows Sandbox Yes in Activity Monitor. This is an Qt app. I generated an Xcode project using qmake, then use Xcode to sign and upload. I tried both manually selecting the profile and letting Xcode manage signing automatically. I've tried both Distribution profiles and Development profiles. It was giving build errors in signing unless I used the --deep flag in Other Code Signing Flags. Then I read online that it's not recommen

App: Nappkin Apple ID: 639242085 Hi, We are getting several Missing API declaration warnings (see below) when submitting our iOS app to the AppStore. Our app doesn't not use the mentioned api's but apparently one or more of the libraries we use do. We have included a privacy manifest that states this fact (included below). Why are we still getting these warnings/errors when we have included a privacy manifest? If each framework used must have a manifest can you tell me which frameworks are in error? We have no influence on the contents of the frameworks used in our apps. How can we comply if a framework we use does not have a required manifest and is unable or unwilling to include it? Our app is a point-of-sale app used by 100's of professionals. We have been in the AppStore for more than 10 years. Our app is fully dependend on several frameworks and not being able to update our app will mean we have to close our business. Thanks! Willem Bison = Privacy manifest ==== NSPrivacyAccessedAPITypes NSPrivacyA

Today, I'm getting Test Flight builds rejected with the following reason: ITMS-90338: Non-public API usage - The app references non-public selectors in MyRedactedAppName: _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, isPassthrough, onSuccess:, removeValuesForKeys:completion However, I'm uploading the exact same code (working on a CI/CD pipeline) as I did last Thursday and that build passed. Pretty sure this is on the Apple side of things. Anyone else seeing this today? I know a few folks have had similar rejections since June 6, when things got updated for WWDC. Some seem to have been resolved by Apple, but I've tested this twice today and received the same result.

Hi I am recieving this mail when I upload an update of my iOS APP: ITMS-91053: Missing API declaration - Your app’s code in the “mi coche eléctrico” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. I have created the PrivacyInfo with this information (the requested in mail), but this mail is recieved even with this PrivacyInfo file in the upadatee app. Any idea what is wrong on it? Thanks in advance

i had upload new build(version 6.8.9) with application loader about 20 hours ago, and loader show success, but the new build 6.9.9 not show in app store connect activity list. when i reupload the version, loader show ERROR ITMS-90189, same build string build exist.how to fix this suitation? is there some bugs in app store connect?

This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution How to sort this? Please help