Open noriHanda opened 1 month ago
greenrobot-team
commented
1 month ago Thanks for making us aware and linking helpful resources!
Based on a quick read there is no immediate requirement. But Apple intends to make this a requirement in the future. So it makes sense to prepare. This also affects the Swift library that the ObjectBox Flutter plugin actually includes.
noriHanda
commented
1 month ago @greenrobot-team Thanks for your reply.
I'm not an expert on this topic and still confused by this like many others, but my impression on reading the Apple document is that any apps/packages that depend on any packages listed need to have the PrivacyManifest. ObjectBox (objectbox_flutter_libs to be precise) seems to be depending on Flutter which is in the list, so I think the priority of this issue is considerably high.
greenrobot-team
commented
1 month ago ObjectBox (objectbox_flutter_libs to be precise) seems to be depending on Flutter which is in the list
Based on the Flutter teams current understanding each dependency has a privacy manifest about the required reason APIs it uses directly. So transitive dependencies like affected Flutter iOS plugins need to (and as you linked above apparently already do) include their own manifest.
And technically, Flutter should already be a direct dependency of any app that uses the ObjectBox Flutter plugins.
Anyhow, if anyone has an issue submitting an app that uses ObjectBox to the Apple App Store let us know the details. Then we can prioritize this.
noriHanda
commented
1 month ago Okay sounds good!
Is there an existing issue?
This package is not explicitly listed in this article, but I believe adding PrivacyInfo.xcprivacy is required to deliver any iOS apps that depend on this package on AppStore nowadays.
Use case
For any iOS apps
Proposed solution
Add PrivacyInfo.xcprivacy file under ios folder. cf. sqflite case
Describe alternatives you've considered
It may not be necessary if this package does not depend on SDK's that require PrivacyManifests.
Additional context
See also: