-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
FCM can't run well in Android Kitkat and JellyBean (not sure about ICS) #759
Comments
oops, sorry i forgot to add the label , thanks for adding it @samtstern I still can't found the solution, i am waiting for your help and guide @samtstern @kroikie . Thanks. |
Hi @dvlwj, FCM is supported from Android 4.0 and later. To clarify you have added the |
@kroikie hi, sorry late respond, working on other project. yes i already declare and added it in the manifest. |
Same problem. |
I also get a lots the same errors predominantly from Asus and Huawei devices. |
I'm facing the same behaviour for android api < 19. Does anybody found a answer for this issue? |
Hi all, @gh-jvr , @cosic , @denmusic1992 Yes, until now I also can't find the solution for this. Last time, my team decided to make a declaration that our App can't support fully for KitKat and JellyBean. Its will be good if we can got answer/solution from @kroikie now. |
hey any body knows the solution? |
My environment
My problem description:
I trigger a push notification in onMessageReceived, and the problem is the push notification on Android Kitkat and Below. When im trying to debug the phone, an error appear as "E/FirebaseInstanceId: Token retrieval failed: PHONE_REGISTRATION_ERROR". This is not happend in other os and device, they all run without problem.
Steps to reproduce:
Observed Results:
E/FirebaseInstanceId: Token retrieval failed: PHONE_REGISTRATION_ERROR
appear.Expected Results:
Relevant Code:
Sorry, i doesn't know how to show the code, since its a privacy from my workplace. Maybe if you tell me which part of the code is important then i can try to show it.
The text was updated successfully, but these errors were encountered: