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

gcm token will sometimes return to the "MESSENGER". #231

Open
fwith opened this issue May 31, 2016 · 14 comments
Open

gcm token will sometimes return to the "MESSENGER". #231

fwith opened this issue May 31, 2016 · 14 comments
Assignees

Comments

@fwith
Copy link

fwith commented May 31, 2016

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.

@lassem
Copy link

lassem commented Jul 7, 2016

Same here, only using the Firebase API:
FirebaseInstanceId.getInstance().getToken()

We've also seen the gcm token returned as "AP".

@AlirezaSadeghi
Copy link

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.

@rajool
Copy link

rajool commented Jul 10, 2016

Same here,
We saw this on the original instance_id service (As we did not switch to Firebase yet)

@texnedo
Copy link

texnedo commented Aug 9, 2016

Does anybody know solution for this issue?

@srihards
Copy link

Same, detecting "MESSENGER" using the Firebase API.

@kroikie kroikie self-assigned this Aug 15, 2016
@kroikie
Copy link
Contributor

kroikie commented Aug 15, 2016

Hi All, this is a known issue and a fix is in progress, I will respond here once the fix is out.

@srihards
Copy link

How long for the issue to be resolved? Our users are getting really angry about not receiving notifications.

@traunay
Copy link

traunay commented Oct 3, 2016

Okay,
So this thing is still going with no fix after a month? I just ran few tests and it happened on devices with 4.2 installed (which I still support)

@pm1100tm
Copy link

pm1100tm commented Oct 25, 2016

Hi, All.
The fix is out? and i have a just simple question.
How can we apply to fixed thing to exiting app if this issue is fiexd?
Will it be done by updating Google Play Service on Android Studio?

@tpurtell
Copy link

tpurtell commented Nov 4, 2016

I am seeing this behavior too.

@dcarey
Copy link

dcarey commented Apr 3, 2017

Me too

@emezias
Copy link

emezias commented Aug 22, 2017

@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.

@eyemwired
Copy link

Check the white papers

@enakhi
Copy link

enakhi commented Jun 4, 2018

BLACKLISTED,MESSENGER,packagename,empty string
we get this codes instead of token

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