You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I identified the crash/bug itself and was able to apply a workaround for the bug.
However on fabric dashboard for broken builds there is no even 'Launch' registered in beta - just "installed". I am sure the "launch" and errors should be both captured by crashlytics.
Even more - as for broken builds an app despite the error/stuck on white sreen - is able to detect a new build - thus I believe that error intercepting should be possible to be initialized earlier as well.
FabricPlugin is unable to catch one error during initialization (white screen shortly after splash screen).
graphql/graphql-js#1182
I identified the crash/bug itself and was able to apply a workaround for the bug.
However on fabric dashboard for broken builds there is no even 'Launch' registered in beta - just "installed". I am sure the "launch" and errors should be both captured by crashlytics.
Even more - as for broken builds an app despite the error/stuck on white sreen - is able to detect a new build - thus I believe that error intercepting should be possible to be initialized earlier as well.
should this be considered as a bug/enhancment?
https://stackoverflow.com/questions/52751138/error-after-startup-of-ionic-app-uncaught-by-crashlytics-fabric
The text was updated successfully, but these errors were encountered: