-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[firebase_crashlytics] Add [FIRApp configure] (FirebaseApp.configure() in Swift) to your application initialization #1411
Comments
Hi @miguelpruivo |
Hi, the minimal code is quite simple, is just exact what is described on the plugin setup:
I believe that these are the relevant verbose logs:
|
A new Crashlytics plugin has now landed on master which should solve this issue. Checkout the migration guide to get started on upgrading to the new Crashlytics plugin: https://firebase.flutter.dev/docs/migration/ |
Steps to Reproduce
Follow the instructions from firebase_crashlytics to set up Crashlytics in your app.
Target Platform: iOS
Devices: All
Logs
As soon as the app starts, it gives the following:
along with
Despite that, the plugin itself seems to be working, at least I can see the Crashlytics up and running on the Firebase console. However, I can't get rid of those errors and somehow it looks like it's expecting
firebase_core
to callconfig
when the Crashlytics itself doesn't require it (unless I'm wrong and if so, the docs are missing it).On Android it seems to be ok.
Flutter doctor
The text was updated successfully, but these errors were encountered: