This issue started after I changed Android apps at OneSignal from Firebase Legacy to FCM… as instructed by “Upcoming Firebase Deprecation” e-mail.
If I remove OneSignal AppID, it runs normally.
Even if I use an old AppID (firebase legacy), it also crashes.
1 Like
Hi @assistsolucoes, thanks for flagging this–we’re currently looking into what might be happening here and how we can fix this. Hang tight and we’ll get you more information as soon as we can.
Thank you!
1 Like
Thanks for your reply.
We need it very soon to finishing update Google’s required API level.
i have the same problem, but i didn’t move from legacy to FCM
how do I solve it?
Hello @pacecode @assistsolucoes @22kifayatun8ne 
We apologize for the inconvenience!
We are happy to announce that we were able to identify the root cause, develop a fix, and release it to production so everything should be working as normal again for you now.
The only thing you will need to do to test your project is to:
- Update your Android Thukable live app to the latest one
- Rebuild your Android app (APK or AAB)
Let us know if you still have any issues.
1 Like