4 ms·
While I think this is a good idea in principle, they way this is currently proposed is very heavy handed. The list of APIs to declare includes things like stand
by shantara 3y ago
While I think this is a good idea in principle, they way this is currently proposed is very heavy handed. The list of APIs to declare includes things like standard NSUserDefaults, which is being used for storing settings and preferences by every single app under the sun.
I’m afraid that this change would predominantly impact only small developers who don’t have a dedicated legal department to deal with this kind of nonsense, and would introduce another reason for bogus app review rejections.
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api?language=objc https://developer.apple.com/documentation/bundleresources/pr...
- nottorp 3y agoI was wondering... so apps makers that want to reduce hassle will have to roll their own way of storing settings? Edit: HUH in all caps. Apple says: "This reason does not permit reading information that was written by other apps or the system, or writing information that can be accessed by other apps." You mean they allow an app to read the settings from another app?
- shantara 3y agoNo. User defaults are already scoped per app. The apps that declare the same app group in the application bundle, can access each other’s data. But this kind of data sharing could be done only with the apps from the same developer, you can’t access data of another arbitrary app.
- nottorp 3y agoThen why do you have to state that particular API's usage?