We have a privacy manifest system in place for plugins that allows plugin developers to declare required reason API usage. However, I didn't consider the case of a non-plugin, pure-Dart package that uses FFI to directly call required reason APIs; we should have a way for packages doing that to declare a manifest and have it bundled into App.framework.
We could probably do this in the Flutter tool, by having it create privacy manifest bundles in App.framework (like what Cocoapods does for static linking). We'd need a way for package developers to declare a manifest that we would bundle; probably a flutter: sub-entry in pubspec.yaml is the best option?
In the meantime, the workaround for this (hopefully very rare) case would be either:
- As the package developer, declare your package as a plugin instead—the native code can be essentially a no-op—and use the podspec (or later, SPM) to bundle a manifest.
- As an app developer, include the reasons at the app level.
We have a privacy manifest system in place for plugins that allows plugin developers to declare required reason API usage. However, I didn't consider the case of a non-plugin, pure-Dart package that uses FFI to directly call required reason APIs; we should have a way for packages doing that to declare a manifest and have it bundled into App.framework.
We could probably do this in the Flutter tool, by having it create privacy manifest bundles in App.framework (like what Cocoapods does for static linking). We'd need a way for package developers to declare a manifest that we would bundle; probably a
flutter:sub-entry inpubspec.yamlis the best option?In the meantime, the workaround for this (hopefully very rare) case would be either: