-
Notifications
You must be signed in to change notification settings - Fork 85
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 Features Suggestion #124
Comments
in addition to this we should probably also put the content of the main into a runeZonedGuard and catch and report the errors to firebase crashlytics. |
@all-contributors please add @TheAmanM for code, maintenance and |
I've put up a pull request to add @TheAmanM! 🎉 |
Good point on the runZoneGuarded. The code, according to Firebase documentation should then be: void main() async {
runZonedGuarded<Future<void>>(() async {
WidgetsFlutterBinding.ensureInitialized();
await Firebase.initializeApp();
FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterFatalError;
runApp(MyApp());
}, (error, stack) =>
FirebaseCrashlytics.instance.recordError(error, stack, fatal: true));
} Also @jorre127, how do you know so much about Flutter? Where do you learn everything from? |
@TheAmanM I work for a company that makes flutter apps, so that helps a lot haha. Just by coming into contact with it everyday I guess. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
@KalleHallden It might be a good idea to implement Firebase Crashlytics and Performance monitoring. These will give you good insight about your app on the Firebase console.
Here is some sample code for implementing Crashlytics, it looks pretty simple:
The text was updated successfully, but these errors were encountered: