-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
gcm token will sometimes return to the "MESSENGER". #231
Comments
Same here, only using the Firebase API: We've also seen the gcm token returned as "AP". |
Same here, We also have seen it sometimes return the package name for the app, as well as sometimes the string "null", which is well, unexpected. |
Same here, |
Does anybody know solution for this issue? |
Same, detecting "MESSENGER" using the Firebase API. |
Hi All, this is a known issue and a fix is in progress, I will respond here once the fix is out. |
How long for the issue to be resolved? Our users are getting really angry about not receiving notifications. |
Okay, |
Hi, All. |
I am seeing this behavior too. |
Me too |
@kroikie Your message says this is a known issue. Can you please elaborate? Is there a bug filed in the AOSP that I can star? Is there any workaround or even a complete problem definition? It's been a while since you took assignment of this issue. If you are busy, maybe another contributor can take this on and get it closed. |
Check the white papers |
BLACKLISTED,MESSENGER,packagename,empty string |
Recently.. Sometimes gcm token, it will be returned to the "MESSENGER".
Gcm token to retrieve them as follows:
InstanceID instanceID = InstanceID.getInstance(getApplicationContext());
String token = instanceID.getToken(getString(R.string.gcm_defaultSenderID), GoogleCloudMessaging.INSTANCE_ID_SCOPE, null);
Most of the cases are sometimes good, but sometimes returned as a token of unknown "MESSENGER".
Are you sure about this? Please tell us if there is a solution.
The text was updated successfully, but these errors were encountered: