After adding PrivacyInfo.xcprivacy following this Steps: https://vikramios.medium.com/itms-91053-missing-api-declaration-3c2bef935bd3 I am getting this error ❌ error: Multiple commands produce 'app_dir/PrivacyInfo.xcprivacy';
Search results for
ITMS-90158
1,681 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
In order to facilitate management, we integrate some SDKs such as Firebase into one of our own internally used SDKs. Recently, when submitted to the appstore, we were prompted that FirebaseCrashing included in the SDK lacked the necessary signature (ITMS-91065). The information that can be confirmed is that after packaging the SDK through secondary packaging, the original signature is lost. And we have a static reference. So what I want to ask is whether we can only manually sign our secondary packaging sdk (the signature is our own certificate different from the original Firebase) to solve this ITMS-91065 problem. According to the description of the Apple Developer Conference, Apple only verifies the consistency and security of the SDK and does not record the signature of each SDK on Apple's servers. Therefore, you should only need to ensure that the SDK is in a signed state to comply with Apple's review requirements. (My guess is still being verified)
While I'm keen on being on the latest version of macOS, I'm having trouble meeting the requirement that my app can run on a version of macOS that doesn't exist :) I'm using Xcode 15.2 (15C500b), targeting iOS 17.2. I've elected to have the App Store choose the minimum version for Catalyst. I've also tried selecting a version. ITMS-90899: Apple silicon Mac support issue - The app is not compatible with the provided minimum macOS version of 14.2. It can run on macOS 14.4 or later. Please specify an LSMinimumSystemVersion value of 14.4 or later in a new build, or select a compatible version in App Store Connect. For details, visit: ... Is there something I could be doing wrong to prompt this behaviour?
One of our apps got hit by the ITMS-91065: Missing Signature issue when we attempted to distribute it to externally via TestFlight. The email said FirebaseCore is missing the signature file within our own framework. After investigation, I realized our recent update to the version of Firebase that has the proper signatures and privacy manifest wasn't enough by itself. Similar to Apple's own instructions on embedding static frameworks since Xcode 15, Firebase instructs us to select the Embed & Sign option. After making the appropriate changes though, we're getting the error in Transporter: Asset validation failed (90085): No architectures in the binary Our setup is as follows: We have an analytics dynamic framework, which depends on Firebase's static framework. The Firebase related frameworks are embedded and signed in our analytics framework. Our app depends on the analytics dynamic framework, which now includes Firebase frameworks within its framework. Since the Firebase frameworks are static, on
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Review
App Store Connect
TestFlight
Hello, which version of xcode are you using ? I have the same issue here : ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/libswiftAssetsLibrary.dylib” file contains “85F4.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryUserDefaults category. Values for NSPrivacyAccessedAPITypeReasons keys in any privacy manifest must be valid reason codes for the corresponding API category. 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. Here the message i have for several items I have tried to embed those with my app but it does not help. Here is my privacy file Thanks in advance :)
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I've complied with the reason declaration following the links sent by the autogenerated emails for the surface level Runner declaration, however libswift has the incorrect values for the reason codes for UserDefaults. I've checked their github and there is no way to add issues since it is read-only. I'm also in the dark for who to contact regarding this. Does anyone have any idea how to resolve this aside from manually changing the privacy files? I don't want to have to do this each time I do pod install. ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/libswiftObjectiveC.dylib” file contains “DDA9.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryUserDefaults category.
Apple send a mail when I publish my ipa. Please correct the following issues, then upload again. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-mountain” that references asset “山青.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-fantasy” that references asset “梦幻.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-bubble” that references asset “泡泡.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-night” that references asset “暗夜.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFB
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?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Xcode
TestFlight
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 just got this error too even though 1) our app icons haven't changed for a long time and many previous builds have been accepted with the same icon set 2) they all render fine in Xcode and 3) I checked the icon locally and the PNG file renders fine. This is the error message in my case: ITMS-90013: Corrupt Image File - The image file 'AppIcon60x60[@]2x.png' appears to be corrupt. I reached out to Apple to see if they have a problem with their backend. Note I enclosed the @ symbol with square brackets so the forum allows me to post this message.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
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.
Hello, I'm encountering an issue with making my app available in the visionOS App Store (Designed for iPad). Here's a detailed walkthrough of the steps I've taken and the problem that arises: I created an archive using Xcode, specifying Apple Vision (Designed for iPad) as the destination. I tested the build on a real Vision Pro device, and it worked fine. I successfully uploaded the build to App Store Connect. After uploading, I received the following email notification: 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 in visionOS. For more information, contact us: https://developer.apple.com/contact. Despite this notification, I consistently accept all required agreements on time. There are no related alerts or banners in either my App Store Connect or Apple Developer dashboards, suggesting a possible error with my Apple Developer Program. Any assistance in resolving thi
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
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