ITMS-90338

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

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

We are received the following error while uploading the application into TestFlight. **ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. ** After sometimes we submit the same application without changing the configurations application submitted successfully into the App Store. We are using the Xcode 15.3 version.

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, our app has been using single size app icon for a while and today when I trying to upload a new version of our app I got an email from App Store Connect saying ITMS-90013: Corrupt Image File - The image file 'AppIcon60x60@2x.png' appears to be corrupt. We haven't touched the image for ages and these 60x60 image were generated by Xcode from the single 1024x1024 image supplied. I've tried to use a new image and still got the same error. Does anyone experienced this recently?

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

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.

We run automated app uploads to Appstore Connect and TestFlight from our company servers, which are behind a firewall. Our firewall is configured to allow connections to the HTTPS servers listed in the Transporter User Guide The problem is, Apple adds new servers (e.g northamerica-1.object-storage.apple.com) to this list without prior announcements and this breaks our automated uploads because our firewalls are not yet updated with the new servers. Transporter logs report vague errors which are difficult to correlate with the new servers that were added. For example, the error msg is: [06:45:19]: [iTMSTransporter] data: null [06:45:19]: [iTMSTransporter] } [06:45:19]: [iTMSTransporter] buildAssetSpi: class BuildRelationshipsBuildAssetDescription { [06:45:19]: [iTMSTransporter] links: class AlbumLocalizationRelationshipsAlbumLinks { [06:45:19]: [iTMSTransporter] self: https://contentdelivery.itunes.apple.com//iris/v1/builds//relationships/buildAssetSpi [06:45:19]: [iTMSTransporter] related: https://contentdeli

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

Greetings everyone, first of all I apologize to everyone for the long question I am going to ask, but I thought it would be better to tell you my question and what I am working on to solve it. You may have heard about Apple's new Privacy Manifest requirement for new apps to be released to the app store. After I heard about it, I made a list of all dependencies used in my project and then updated them to the versions that include the Privacy Manifest file. Since I only use UserDefaults in my project, which is one of the required reason APIs specified by Apple, I added it and my reason for using it in the Privacy Manifest file. When I released a package with this development, I received a new notification email from Apple saying that while they used to be upset with me about UserDefaults, they are no longer, so it seems that Apple has accepted my reason for using UserDefaults in the application. However, Apple was also upset about Required Reason APIs in this list that I don't actually use (e.g. SystemBootTime

Older version of xcode 14.3.1 is uploading build with notice to update xcode version but newer version of xcode 15.3.1 and beta giving the error below. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Shared.framework/Shared: _SSL_CTX_free, _SSL_CTX_new, _SSL_CTX_set_alpn_protos, _SSL_CTX_set_options, _SSL_do_handshake, _SSL_free, _SSL_get0_alpn_selected, _SSL_get_error, _SSL_get_session, _SSL_new, _SSL_read, _SSL_set_alpn_protos, _SSL_set_bio, _SSL_set_connect_state, _SSL_write. 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 in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.