Search results for

“ITMS-90338”

1,703 results found

Post

Replies

Boosts

Views

Activity

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
836
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
663
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
672
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
ITMS-91055: Invalid API reason declaration
in this weeks i received this error: ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “VanigliaPro” file contains “App Functionality” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryFileTimestamp category. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, values for NSPrivacyAccessedAPITypeReasons keys in your app’s 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. ITMS-91053: Missing API declaration - Your app’s code in the “xxxx” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDe
1
0
3k
Apr ’24
What's wrong in my PrivacyInfo file in iOS App? I still recieve a mail with TMS-91053: Missing API declaration when upload an upadte
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
3
0
993
Apr ’24
When using a library with SPM, I always receive an email from App Store Connect regarding the PrivacyAccessedAPI issue.
Hello. I'm having an issue using SPM to include a privacy manifest in my project. For example, if I use Alamofire 5.9.0 (with the PrivacyInfo.xcprivacy file) using SPM, I am continuously receiving the email saying ITMS-91053: Missing API declaration - System Boot Time when submitting an app for review. But use the same version of Alamofire using cocoapod(as a dynamic library), the PrivacyAccessedAPI issue will not occur. Is there any resolution for this problem? If I use a library using SPM, do I need to add the library's information in the main app's PrivacyInfo.xcprivacy file? Thank you.
0
0
528
Apr ’24
Are you still running the new Privacy Manifest checks on our builds today?
I just submitted a build to TestFlight this morning that should have set off the same alarms as last week, but it didn't. We received no emails complaining about ITMS-91053 violations like happened on this branch before. We've been working hard to figure out how to meet your new privacy requirements, and it's been quite frustrating. I thought I finally fixed it yesterday, but today I wanted to run a sanity test. I went back and created a build that should fail, but now that one is apparently fine as well. I'm at a complete loss.
1
0
585
Apr ’24
ITMS-90238: Invalid Signature - The main app bundle Tren at path Tren.app has following signing error(s): a sealed resource is missing or invalid
Hello, I'm create an app using QT on MacOs with Generate to Xcode, when submitting it to the App Store the upload process was successful but I got email feedback with the message containing the following: ITMS-90238: Invalid Signature - The main app bundle Tren at path Tren.app has following signing error(s): a sealed resource is missing or invalid . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple .com/library/mac/technotes/tn2206/_index.html for more information. ITMS-90296: App sandbox not enabled - The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[Tren.app/Contents/MacOS/Tren ]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app.
1
0
1.1k
Mar ’24
Xamarin Forms - API Declaration not working
Morning All, just wanted a little help with my xamarin forms app. When I publish to test flight for a public test build I am always receiving the email about ITMS-91053: Missing API declaration. I have followed the steps and created a PrivacyInfo.xcprivacy in Xcode and I can see it in my xamarin iOS project but I still get the email saying it is missing. Is there something I am missing or ned to reference in the info.plist etc. My looks like the following: `
2
0
1.6k
Mar ’24
libswift ITMS-91055: Invalid API reason declaration
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.
3
0
1.7k
Mar ’24
AppStoreConnect upload error ITMS-90432 - Unexpected file found in Frameworks
Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?
1
0
1.4k
Mar ’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
Replies
0
Boosts
0
Views
836
Activity
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.
Replies
0
Boosts
0
Views
663
Activity
Apr ’24
ITMS-90725: SDK version issue
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
Replies
1
Boosts
0
Views
1.5k
Activity
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
Replies
0
Boosts
0
Views
1.2k
Activity
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).
Replies
0
Boosts
0
Views
672
Activity
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
Replies
1
Boosts
0
Views
2.2k
Activity
Apr ’24
error: Multiple commands produce '.../PrivacyInfo.xcprivacy
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';
Replies
4
Boosts
0
Views
2.6k
Activity
Apr ’24
ITMS-91055: Invalid API reason declaration
in this weeks i received this error: ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “VanigliaPro” file contains “App Functionality” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryFileTimestamp category. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, values for NSPrivacyAccessedAPITypeReasons keys in your app’s 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. ITMS-91053: Missing API declaration - Your app’s code in the “xxxx” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDe
Replies
1
Boosts
0
Views
3k
Activity
Apr ’24
What's wrong in my PrivacyInfo file in iOS App? I still recieve a mail with TMS-91053: Missing API declaration when upload an upadte
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
Replies
3
Boosts
0
Views
993
Activity
Apr ’24
When using a library with SPM, I always receive an email from App Store Connect regarding the PrivacyAccessedAPI issue.
Hello. I'm having an issue using SPM to include a privacy manifest in my project. For example, if I use Alamofire 5.9.0 (with the PrivacyInfo.xcprivacy file) using SPM, I am continuously receiving the email saying ITMS-91053: Missing API declaration - System Boot Time when submitting an app for review. But use the same version of Alamofire using cocoapod(as a dynamic library), the PrivacyAccessedAPI issue will not occur. Is there any resolution for this problem? If I use a library using SPM, do I need to add the library's information in the main app's PrivacyInfo.xcprivacy file? Thank you.
Replies
0
Boosts
0
Views
528
Activity
Apr ’24
Are you still running the new Privacy Manifest checks on our builds today?
I just submitted a build to TestFlight this morning that should have set off the same alarms as last week, but it didn't. We received no emails complaining about ITMS-91053 violations like happened on this branch before. We've been working hard to figure out how to meet your new privacy requirements, and it's been quite frustrating. I thought I finally fixed it yesterday, but today I wanted to run a sanity test. I went back and created a build that should fail, but now that one is apparently fine as well. I'm at a complete loss.
Replies
1
Boosts
0
Views
585
Activity
Apr ’24
ITMS-90238: Invalid Signature - The main app bundle Tren at path Tren.app has following signing error(s): a sealed resource is missing or invalid
Hello, I'm create an app using QT on MacOs with Generate to Xcode, when submitting it to the App Store the upload process was successful but I got email feedback with the message containing the following: ITMS-90238: Invalid Signature - The main app bundle Tren at path Tren.app has following signing error(s): a sealed resource is missing or invalid . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple .com/library/mac/technotes/tn2206/_index.html for more information. ITMS-90296: App sandbox not enabled - The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[Tren.app/Contents/MacOS/Tren ]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app.
Replies
1
Boosts
0
Views
1.1k
Activity
Mar ’24
Xamarin Forms - API Declaration not working
Morning All, just wanted a little help with my xamarin forms app. When I publish to test flight for a public test build I am always receiving the email about ITMS-91053: Missing API declaration. I have followed the steps and created a PrivacyInfo.xcprivacy in Xcode and I can see it in my xamarin iOS project but I still get the email saying it is missing. Is there something I am missing or ned to reference in the info.plist etc. My looks like the following: `
Replies
2
Boosts
0
Views
1.6k
Activity
Mar ’24
libswift ITMS-91055: Invalid API reason declaration
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.
Replies
3
Boosts
0
Views
1.7k
Activity
Mar ’24
AppStoreConnect upload error ITMS-90432 - Unexpected file found in Frameworks
Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?
Replies
1
Boosts
0
Views
1.4k
Activity
Mar ’24