Open bgintzairspace opened 1 month ago
Hi @bgintzairspace, I'm not quite sure if I get your concern. Could you please provide more context?
Hey @bgintzairspace. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
@SelaseKay Sorry for the delay. Basically, I would like to use the FirebaseCrashlytics.instance.recordFlutterError, but I want to handle reporting to the console myself (after filtering, etc), so I would prefer to not have teh recordFlutterError automatically call FlutterError.presentError (firebase_crashlytics.dart:141 and firebase_crashlytics:160). The FirebaseCrashlytics.instance.recordError has the printDetails option to skip this sort of thing, I was hoping it could be added to the recordFlutter[XXX] methods too
Using Crashlytics forces you to use the presentError method even if you overrode onError to not have it presented.