Post not yet marked as solved
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
Post not yet marked as solved
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 :)
Post not yet marked as solved
Hi, I have been receiving an email error message: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. when submitting an app to the App Store Connect using xcode. I have searched for many solutions online, but none of them have worked. Later, I manually created the SwiftSupport directory and copied the Swift dynamic library (dylib) that the app depends on to this directory, as well as copying them to the. app/Frameworks directory. After submitting, I received an email saying that these. dylib dynamic libraries are not in the. app/Frameworks directory. I opened the IPA file and checked the directory, and I really saw that they are located below. I don't know where the problem is, can you tell me the exact reason?
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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.
Post not yet marked as solved
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.
Post not yet marked as solved
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?
Post not yet marked as solved
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.
Post not yet marked as solved
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
Post not yet marked as solved
Only Apple can say what the status of their scanning is. My understanding is that submitting for review does trigger the scans. There are some interpretations of the rules that suggest that resubmitting the app with the same SDKs that were already approved for the app will not be rejected. Perhaps you experience is this rule in action. This developer forums post suggests that apps are being rejected due to issues with privacy manifests: ITMS-91054: Invalid API category declaration
Post not yet marked as solved
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
Post not yet marked as solved
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.
Post not yet marked as solved
I have been able to also reproduce the issue with a Xcode 15.3 template project after adding Apple Vision as a supported destination, configuring Xcode Cloud and adding a TestFlight post-action (without the post-action, the archives succeed). Submitted FB13774427 (Xcode Cloud visionOS archive action fails for iOS template project with Apple Vision added as supported destination.) as this might be a bug. Anybody successfully building these visionOS/iOS hybrid apps with current version Xcode Cloud after including a TestFlight post-action? The following email references ITMS error numbers: TMS-90508: Invalid Info.plist value - The value for the key 'DTPlatformName' in bundle DualUse.app is invalid. ITMS-90039: Type Mismatch - The value for the Info.plist key CFBundleIcons.CFBundlePrimaryIcon is not of the required type for that key. See the Information Property List Key Reference at https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Introduction/Introd
Post not yet marked as solved
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
