Skip to content
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

uncaptured error during startup #142

Open
ciekawy opened this issue Oct 11, 2018 · 1 comment
Open

uncaptured error during startup #142

ciekawy opened this issue Oct 11, 2018 · 1 comment

Comments

@ciekawy
Copy link

ciekawy commented Oct 11, 2018

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

@frederikhors
Copy link

Working with Sapper and "graphql": "15.0.0" today and here we are!

Temporarily fixed by building with NODE_ENV=production. But something is broken I think. 🤕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants