Apple Privacy Manifest

[AntonGolikov]

Summary

Starting on May 1 Apple will require to provide a reason of using certain API. Docs: Describing use of required reason API

The framework uses UserDefaults API (here or here) for iOS, so Apple will require a Manifest file in order to be accepted in AppStore.

Is this something the team is aware of and/or have plans to update?

[kevinresol]

There is no planned update to this repo but PRs are welcome.

[Yandamuri]

@AntonGolikov , I have recently(Obviously after May 1'st) submitted an updated to Appstore and I have not done changes to as you mentioned here. but still my app was accepted. By the time i submit the app I was using react-native-default-preference: 1.4.3

So, I guess Appstore is ok the library. Please correct me if I am missing something here.

[AntonGolikov]

@Yandamuri In one of the issue thread in expo repo about this, one of the maintainers mentioned (at the time) that Apple will ignore the declaration manifest in third parties by the deadline. He mentioned that it is common by Apple to rollout a feature/requirement, give little time to do it and move deadlines or alter the requirements.

We still expect this to become an issue somewhere in the future. Or Apple will simply use privacy manifest from the main app and third parties' manifests remain optional

[Yandamuri]

@AntonGolikov Do you still have the link to the Expo issue thread?

BTW, Are you still using the same package(Because, it's been a while since you have raised this issue.) or moved to any alternative?

[AntonGolikov]

@Yandamuri Unfortunately, I can't find it now. It's burrowed somewhere in related issue threads.

We found out, that we're not using this package anywhere in code, so we just remove it form dependencies.