[firebase_crashlytics] Enable Firebase Crashlytics at runtime #5581
Unanswered
lschmierer
asked this question in
Feature request
Replies: 1 comment 1 reply
-
This has been resolved in the Crashlytics update: https://firebase.flutter.dev/docs/crashlytics/usage#enable-opt-in-reporting |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
To be compliant with European privacy laws, we are required to get user consent before transmitting data to Crashlytics.
We want to use Crashlytics as described at https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=ios#enable_opt-in_reporting
This is, however, not possible with the Flutter library at the moment, as Fabric is always initialised as soon as the plugin is attached to the engine.
A possible fix would be to wait for the first MethodCall to be received by the plugin and initialiseFabric after that.
That way a library user can take care to not make any calls to Crashlytics before user consent is given.
Beta Was this translation helpful? Give feedback.
All reactions