Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

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
3.0k
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
969
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
519
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
566
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
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.6k
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.3k
Mar ’24
Reply to Code Signing failed for third-party Swift package
Xcode Archive Open archives window Show in finder Show package contents Go to /Products/Applications/%YOUR_APP%.app/Contents/Frameworks/ Backup deleted files, delete google frameworks that cause error ITMS-90238, GoogleAppMeasurementIdentitySupport.framework, FirebaseAnalytics.framework etc Upload modified archive again from Xcode Archives window Look to the size of frameworks, this is something wrong with it. After all build processing completed and I check work in TestFlight and all ok
Topic: Code Signing SubTopic: General Tags:
Mar ’24
When submitting for Apple review, you will receive a warning email about the required reason APIs from the third party SDK.
Hello, I have a question regarding the Privacy Manifest of a third-party SDK. We are using a static third-party SDK. This third-party SDK use the UserDefaults API, and it is also specified in the Privacy Accessed API Types within PrivacyInfo.xcprivacy. The static third-party SDK is added as a dependency via CocoaPods, and PrivacyInfo.xcprivacy is included in the Pods Resource. Additionally, our app does not use UserDefaults API. When we generate the Privacy Report, it correctly shows the data collected by the third-party SDK. However, when we submitted for review, we received a warning email stating that UserDefaults is being used in the app but is missing from the Privacy Manifest. ITMS-91053: Missing API declaration - Your app’s code in the “MyApp” 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 inc
3
0
2.6k
Mar ’24
What role/permissions/privileges needed to get emails regarding app review submissions
Am tired of asking my boss to forward me the emails they get from Apple with the subject The uploaded build for XXXX has one or more issues. I am trying to debug issues such as ITMS-91053: Missing API declaration as we deal with our 3rd party package usage. What permissions, privileges do I need to get those emails?
2
0
789
Mar ’24
How to find usages of Reason Required API?
We are getting warnings from Apple, ITMS-91053 Missing API declaration, for categories Disk Space, Timestamp, and more. But we've checked our source code to make sure we are not making any of the entry points at issue. We suspect they are being called from one of the 3rd party frameworks we use, some of them are binary xcframeworks. Is Apple planning on extending their warnings to provide more information about where the usages are? Are we left to find it ourselves? Do we need to resort to adding those reasons to our app's manifest? Which seems hacking since we probably don't know when of the allowed reasons are accurate.
4
0
2.0k
Mar ’24
Reply to Code Signing failed for third-party Swift package
App Store Connect Hello, We noticed one or more issues with a recent delivery for the following app: Version 24.3.4 Build 2.1.0 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90291: Malformed Framework - The framework bundle FirebaseFirestoreInternal (------.app/Contents/Frameworks/FirebaseFirestoreInternal.framework) must contain a symbolic link 'FirebaseFirestoreInternal' -> 'Versions/Current/FirebaseFirestoreInternal'. Refer to the Anatomy of Framework Bundles for more information.
Topic: Code Signing SubTopic: General Tags:
Mar ’24
How do I link directly to a private app page in the App Store?
When an update is available for my unlisted private app, I would like to notify my users. That part is easy. As part of this notification, I would like to give my users the option to click a button sending them directly to a page in the App Store, where they can update the app. I cannot figure out how to do this. I have tried with the following links: https://apps.apple.com/app/id https://apps.apple.com/us/app/vh-ordrer/id itms-apps://itunes.apple.com/app/id But all of the links give me the same message: App not available: This app is currently not available in your country or region. The app is made available through MDM. Is there a way to generate a direct link to the App Store page for my Private app? If not, then I would like to know if there is a way to link users directly to the Account pop over in the App Store?
0
0
380
Mar ’24