Logging non-fatal exceptions

Sometimes there are exceptions that do/should not crash the applications. Would be great if there was the possibility of logging it with Crashlitics::logException.

[jaumard]

@jaggernod I’m doing the iOS side and in fact by using the API I notice that logError and logException are maybe not needed…

I just add a reportCrash() method to be able to support Zone reporting, so it mean that it will do same as logError and logException…

So my idea is to remove those and just have an reportError (who can handle exception or error). What do you think ?

Basically now the main will look like this:

void main() {
  bool isInDebugMode = false;

  FlutterError.onError = (FlutterErrorDetails details) {
    if (isInDebugMode) {
      // In development mode simply print to console.
      FlutterError.dumpErrorToConsole(details);
    } else {
      // In production mode report to the application zone to report to
      // Crashlytics.
      Zone.current.handleUncaughtError(details.exception, details.stack);
    }
  };

  runZoned<Future<Null>>(() async {
    runApp(MyApp());
  }, onError: (error, stackTrace) async {
    // Whenever an error occurs, call the `reportCrash` function. This will send
    // Dart errors to our dev console or Crashlytics depending on the environment.
    await FlutterCrashlytics().reportCrash(error, stackTrace, forceCrash: false);
  });
}

[shyjuzz]

@jaumard Thank you for the reply. I couldnt see the non-fatal exception in the dashborad after 3 days as well and my project is working fine in the debug mode but gettiing the following exception in the release mode. Please help

`* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:dynamicProfileRuntimeClasspath'.
   > Could not resolve project :flutter_crashlytics.
     Required by:
         project :app
      > Could not select value from candidates [null, debug, release] using AlternateDisambiguationRule.BuildTypeRule.
         > java.lang.NullPointerException (no error message)`

I could fix it with

lintOptions {
        checkReleaseBuilds false
    }