You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The SDK doesn't disclose in the new Privacy Manifest what purposes it uses the new required reason APIs. When Apple starts sending notices out to teams, lots of the usage is going to originate from your SDK. Apple states on their developer page that they will start notifying teams that are using 'required reason' APIs Fall 2023. App submissions will be rejected in Spring 2024.
Describe the solution you'd like
Implement Apple's new Privacy Manifest which has been a think since Xcode 15 this fall (summer if counting beta).
Specifically, implement the required reason usage part. Even usage of UserDefaults will flag an app as needing to disclose why it uses that API.
Thanks for opening the issue. We are already talking internally to provide a Apple Privacy Manifest. Team will provide an update on the issue once we have it available.
Is your feature request related to a problem? Please describe.
The SDK doesn't disclose in the new Privacy Manifest what purposes it uses the new required reason APIs. When Apple starts sending notices out to teams, lots of the usage is going to originate from your SDK. Apple states on their developer page that they will start notifying teams that are using 'required reason' APIs Fall 2023. App submissions will be rejected in Spring 2024.
Describe the solution you'd like
Implement Apple's new Privacy Manifest which has been a think since Xcode 15 this fall (summer if counting beta).
Specifically, implement the required reason usage part. Even usage of UserDefaults will flag an app as needing to disclose why it uses that API.
Check the full list of affected APIs and description of the manifest changes here: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api#
Related to #3326
Describe alternatives you've considered
There isn't any alternatives for this one.
Is the feature request related to any of the existing Amplify categories?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: