-
Notifications
You must be signed in to change notification settings - Fork 426
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
Crash observed in firebase logs #2250
Comments
I will add an exception handler to catch this case. |
Thanks, @christocracy, kindly let us know if it is done. We will pull the latest SDK |
Hi @christocracy any update on this crashes , number of crashes spiked and it is impacting on our user base. Please fix this crashes and let us know so that we can updated our transistor sdk |
Hi @christocracy Could you please help us on this issues, the number of crashes are rapidly growing and its impacting on our app functionality. please provide fix for this crashes. |
Hi @christocracy, This issue was reported 3 weeks ago, and we still don't have a fix yet. I would appreciate any updates on this issue, as the number of crashes in Firebase is increasing day by day. |
Released to |
Hi @christocracy, build failed with new version of transistor sdk "react-native-background-geolocation": "4.18.4" HeadlessTaskManager.java:12: error: cannot find symbol Previously we were using the version 4.17.6 and didn’t face this issue before. // @Suryamadhu9346 |
It’s time for you to upgrade your react native version. You’re far behind. |
Understood. However, the react native version upgrade is a significant task, as other dependency packages will also need to be upgraded. Any alternative suggestions would be appreciated. |
There are no alternative. It’s time to pay up on your technical debt. |
Your Environment
react-native -v
): 0.66.5Expected Behavior
Should not crash.
Actual Behavior
there were 4 users facing crash issue from firebase console.
Device states: 100% background
Steps to Reproduce
Since the crashes were reported from firebase console, there are no reporduce step.
Context
User using the app.
Debug logs
Logs
The text was updated successfully, but these errors were encountered: