-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[native_assets_cli] iOS/MacOS privacy manifest #878
Comments
Discussing with @mosuem we have multiple options that we can pursue with adding new asset types that are connected to existing asset types: API options1.
|
cc @HosseinYousefi as well for discussion on how to deal with "assets-that-belong-to-other-assets" or "assets-that-augment-other-assets". |
Option2, but in it's own package. I would try to keep things simple, and have a new asset type for the class PrivacyManifestAsset implements Asset{
final Sting nativeCodeAssetId;
...
}
Asset buildPrivacyManifest(NativeCodeAsset library, PrivacyManifestOptions options) { ... }
What do you mean? |
In the most general form, the thing we're building could be a graph, not a tree. So using
What if |
Note from discussion with @mkustermann
Deprioritizing because the list of required reason APIs is quite small. |
When using something like the camera on iOS/MacOS, the dylib needs to be bundled with a privacy manifest about why the permission is needed.
We need some way to communicate a privacy manifest from
build.dart
to Flutter.This could possibly be a new asset type.
We need to check if we need a privacy manifest per dylib or just per Dart package.
The text was updated successfully, but these errors were encountered: