Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Reply to Details on ITMS-90984: Apple Vision Pro support issue
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
May ’24
Reply to Describing use of required reason API - current status
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
Topic: Privacy & Security SubTopic: General Tags:
May ’24
Describing use of required reason API - current status
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
1
0
886
May ’24
ITMS-91054: Invalid API category declaration
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.
3
0
2.2k
May ’24
Reply to Xcode Cloud Archive - visionOS fails with Info.plist errors?
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
May ’24
iTMS Transporter Servers | Bad Status received from server: 401
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
0
0
590
Apr ’24
MIssing API declaration warning on AppStore submission
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
2
0
814
Apr ’24
Understanding Apple’s new Privacy Manifest Rules
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
0
0
2.3k
Apr ’24
We started receiving this error on newer version of xcode 15+ while uploading build
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.
0
0
301
Apr ’24
ITMS-90863: Macs with Apple silicon support issue - The app uses symbols that aren’t present in macOS
Hi all, I got this error from test flight /System/Library/Frameworks/_PassKit_SwiftUI.framework/_PassKit_SwiftUI _$s16_PassKit_SwiftUI03AddA14ToWalletButtonVAA0cD09EmptyViewVRszrlE6actionACyAFGyyc_tcfC _$s16_PassKit_SwiftUI03AddA14ToWalletButtonVMn _$s16_PassKit_SwiftUI03AddA14ToWalletButtonVyxG0cD04ViewAAMc _$s16_PassKit_SwiftUI03AddA19ToWalletButtonStyleV5blackACvgZ _$s16_PassKit_SwiftUI03AddA19ToWalletButtonStyleVMa _$s7SwiftUI4ViewP09_PassKit_aB0E03addD19ToWalletButtonStyleyQrAD03AdddghiJ0VF _$s7SwiftUI4ViewP09_PassKit_aB0E03addD19ToWalletButtonStyleyQrAD03AdddghiJ0VFQOMQ I removed support for MacOS and Vision Pro I tried to add Passkit and SwiftUI . framework But I got other error when I try to upload to test flight Xcode 15.3 Do you have some suggestion? thanks
0
0
813
Apr ’24
ITMS-90053 Mac Catalyst Invalid Binary
I am really stuck. I uploaded my Mac Catalyst app. The binary passes validation beforehand. I submit for review. After being in waiting for review for a couple of minutes it is rejected with invalid binary and comes back with an email saying ITMS-90053: This bundle is invalid - The bundle identifier is already in use by a different software package. The only app that is using the same bundle is the IOS version where I added the Mac platform.
0
0
650
Apr ’24
Cordova-ios 7.1.0: ITMS-91053: Missing API declaration after adding privacy manifest
Hey, I’m updating all of my apps to target the new versions of all the plugins we use, and for some reason, I have a warning message : 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. ... 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: NSPrivacyAccessedAPICategoryFileTimestamp. ... Apple Developer Relations But in my Cordova config.xml, I have already added the tag: NSPrivacyTracking NSPrivacyCollectedDataTypes NSPrivacyTrackingDomains NSPrivacyAccessedAPITypes NSPrivacyAccessedAPIType NSPrivacyAccessedAPICategoryDiskSpace NSPrivacyAccessedAPITypeReasons E174.1 NSPrivacyAccessedAPIType NSPrivacyAccessedAPICategoryFileTimestamp NSPrivacyAccessedAPITypeReasons 3B52.1 I have already sent some applications to Apple
0
0
1.2k
Apr ’24
ITMS-90809: Deprecated API Usage
Hello, Trying to upload build to AppStore but reciving ITMS-90809: Deprecated API Usage. We have tried all possible solutions i think. Searching some help and advice here. All help is appreciated. cmd + shift + f) to find if UIWebView command grep -r UIWebView. Searched out in the code. There is no web view WKwebview is used in every file ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).
0
0
622
Apr ’24
Missing API declaration Help
Hey, I uploaded an app to Testflight and received these two Missing API declaration warnings. Is there something I am missing/wrong on the PrivacyInfo.xcprivacy file? Thanks so much! 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: NSPrivacyAccessedAPICategoryFileTimestamp. 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. 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 NSPrivacyAccessedAPIType
1
0
2.2k
Apr ’24