UserDefaults api requires reason for use in the privacy manifest
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 4d 48m
- Merged PRs (30d)
- 1
Description
Describe the bug
UserDefaults api is used in your codebase so it requires adding a reasons for use in your privacy manifest
Refer to this document from Apple:
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api
Expected behavior
A required reason should be included in the privacy manifest
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the UserDefaults usage and the existing privacy manifest in the AppAuth-iOS codebase, then read Apple's required-reason API guidance linked in the issue. Add the appropriate required-reason entry to the manifest and verify that the project includes it correctly for the affected iOS or macOS targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100