Why does firebase push_token return Blacklisted?
I am implementing Firebase messaging in my app.
While I am testing the app sends the refreshed_token to my database, but in live production environment (Play store) it returns 'BLACKLISTED' as push_token.
Does someone know why this happen? Or what I can do to fix this problem.
Can't find others with the same problem.
I use the code from the Firebase documentation.
@Override
public void onTokenRefresh() {
super.onTokenRefresh();
String refreshedToken = FirebaseInstanceId.getInstance().getToken();
Log.d(TAG, "Refreshed token: " + refreshedToken);
sendTokenToServer(refreshedToken);
}
The sendTokenToServer method posts the token to my api and inserts in the database.
android firebase push-notification firebase-cloud-messaging edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
add a comment |
I am implementing Firebase messaging in my app.
While I am testing the app sends the refreshed_token to my database, but in live production environment (Play store) it returns 'BLACKLISTED' as push_token.
Does someone know why this happen? Or what I can do to fix this problem.
Can't find others with the same problem.
I use the code from the Firebase documentation.
@Override
public void onTokenRefresh() {
super.onTokenRefresh();
String refreshedToken = FirebaseInstanceId.getInstance().getToken();
Log.d(TAG, "Refreshed token: " + refreshedToken);
sendTokenToServer(refreshedToken);
}
The sendTokenToServer method posts the token to my api and inserts in the database.
android firebase push-notification firebase-cloud-messaging edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
We have the same problem. Any news about this strange behaviour?
– DreamOfMirrors
Feb 11 '17 at 11:41
@DreamOfMirrors No news :( , still experiencing the same problem.. Did you find a solution?
– sj0rske
Feb 14 '17 at 17:06
1
This just happened to me too, the only thing I can add is that this came from an Android device (My app runs on Android & iOS) and that I read somewhere (can't find where) that this may be related to the app being run on emulators.
– kR105
Feb 20 '17 at 9:06
@kR105 If it happens to be that emulators are blacklisted and when I look at my Firebase statistic I currently have 3 blacklisted devices in my database and 3 foreign country's registered in Firebase that are not related to my app. So these device can be emulators. Still not sure...
– sj0rske
Feb 20 '17 at 22:48
add a comment |
I am implementing Firebase messaging in my app.
While I am testing the app sends the refreshed_token to my database, but in live production environment (Play store) it returns 'BLACKLISTED' as push_token.
Does someone know why this happen? Or what I can do to fix this problem.
Can't find others with the same problem.
I use the code from the Firebase documentation.
@Override
public void onTokenRefresh() {
super.onTokenRefresh();
String refreshedToken = FirebaseInstanceId.getInstance().getToken();
Log.d(TAG, "Refreshed token: " + refreshedToken);
sendTokenToServer(refreshedToken);
}
The sendTokenToServer method posts the token to my api and inserts in the database.
android firebase push-notification firebase-cloud-messaging edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
I am implementing Firebase messaging in my app.
While I am testing the app sends the refreshed_token to my database, but in live production environment (Play store) it returns 'BLACKLISTED' as push_token.
Does someone know why this happen? Or what I can do to fix this problem.
Can't find others with the same problem.
I use the code from the Firebase documentation.
@Override
public void onTokenRefresh() {
super.onTokenRefresh();
String refreshedToken = FirebaseInstanceId.getInstance().getToken();
Log.d(TAG, "Refreshed token: " + refreshedToken);
sendTokenToServer(refreshedToken);
}
The sendTokenToServer method posts the token to my api and inserts in the database.
android firebase push-notification firebase-cloud-messaging android firebase push-notification firebase-cloud-messaging edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
edited Feb 9 '17 at 14:45
Frank van Puffelen
243k29387415
243k29387415
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
asked Feb 9 '17 at 11:57
sj0rskesj0rske
177211
177211
We have the same problem. Any news about this strange behaviour?
– DreamOfMirrors
Feb 11 '17 at 11:41
@DreamOfMirrors No news :( , still experiencing the same problem.. Did you find a solution?
– sj0rske
Feb 14 '17 at 17:06
1
This just happened to me too, the only thing I can add is that this came from an Android device (My app runs on Android & iOS) and that I read somewhere (can't find where) that this may be related to the app being run on emulators.
– kR105
Feb 20 '17 at 9:06
@kR105 If it happens to be that emulators are blacklisted and when I look at my Firebase statistic I currently have 3 blacklisted devices in my database and 3 foreign country's registered in Firebase that are not related to my app. So these device can be emulators. Still not sure...
– sj0rske
Feb 20 '17 at 22:48
add a comment |
We have the same problem. Any news about this strange behaviour?
– DreamOfMirrors
Feb 11 '17 at 11:41
@DreamOfMirrors No news :( , still experiencing the same problem.. Did you find a solution?
– sj0rske
Feb 14 '17 at 17:06
1
This just happened to me too, the only thing I can add is that this came from an Android device (My app runs on Android & iOS) and that I read somewhere (can't find where) that this may be related to the app being run on emulators.
– kR105
Feb 20 '17 at 9:06
@kR105 If it happens to be that emulators are blacklisted and when I look at my Firebase statistic I currently have 3 blacklisted devices in my database and 3 foreign country's registered in Firebase that are not related to my app. So these device can be emulators. Still not sure...
– sj0rske
Feb 20 '17 at 22:48
We have the same problem. Any news about this strange behaviour?
– DreamOfMirrors
Feb 11 '17 at 11:41
We have the same problem. Any news about this strange behaviour?
– DreamOfMirrors
Feb 11 '17 at 11:41
@DreamOfMirrors No news :( , still experiencing the same problem.. Did you find a solution?
– sj0rske
Feb 14 '17 at 17:06
@DreamOfMirrors No news :( , still experiencing the same problem.. Did you find a solution?
– sj0rske
Feb 14 '17 at 17:06
1
1
This just happened to me too, the only thing I can add is that this came from an Android device (My app runs on Android & iOS) and that I read somewhere (can't find where) that this may be related to the app being run on emulators.
– kR105
Feb 20 '17 at 9:06
This just happened to me too, the only thing I can add is that this came from an Android device (My app runs on Android & iOS) and that I read somewhere (can't find where) that this may be related to the app being run on emulators.
– kR105
Feb 20 '17 at 9:06
@kR105 If it happens to be that emulators are blacklisted and when I look at my Firebase statistic I currently have 3 blacklisted devices in my database and 3 foreign country's registered in Firebase that are not related to my app. So these device can be emulators. Still not sure...
– sj0rske
Feb 20 '17 at 22:48
@kR105 If it happens to be that emulators are blacklisted and when I look at my Firebase statistic I currently have 3 blacklisted devices in my database and 3 foreign country's registered in Firebase that are not related to my app. So these device can be emulators. Still not sure...
– sj0rske
Feb 20 '17 at 22:48
add a comment |
3 Answers
3
active
oldest
votes
from Firebase support:
Hi there,
It seems that this is a known minor issue with our internal infrastructure where the device used for the Play Store review can be BLACKLISTED by GCM / FCM in some occasions. However, this should not affect your real users.
We are looking beyond Firebase and working with Play Store team to avoid this inconvenience.
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
add a comment |
I can conclude after researching this problem that when an emulator runs the app Firebase will return BLACKLISTED. Also thanks to @kR105
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
2
I saw this morning in my server log that a Nexus 5X sent me a BLACKLISTED token so it seems it can occur to a real device. Strange.
– fralbo
Apr 6 '17 at 6:31
@2ndGAB are you sure it is not an emulated device? Or how can you be sure?
– sj0rske
Apr 6 '17 at 6:33
I cannot be sure at 100%, But that would be surprising that a developper uses my application webservices to make some tests.
– fralbo
Apr 6 '17 at 7:00
I also have a Nexus 5X BLACKLISTED, I am not using an emulator.
– Dieter Donnert
Aug 2 '17 at 17:58
No,I have quite a few user getting BLACKLISTED...
– ken
Oct 18 '17 at 16:49
|
show 4 more comments
The App will be running on an emulator hence Firebase token will be Blacklisted
answered Nov 16 '18 at 8:50
RamaRama
1
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f42136122%2fwhy-does-firebase-push-token-return-blacklisted%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
from Firebase support:
Hi there,
It seems that this is a known minor issue with our internal infrastructure where the device used for the Play Store review can be BLACKLISTED by GCM / FCM in some occasions. However, this should not affect your real users.
We are looking beyond Firebase and working with Play Store team to avoid this inconvenience.
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
add a comment |
from Firebase support:
Hi there,
It seems that this is a known minor issue with our internal infrastructure where the device used for the Play Store review can be BLACKLISTED by GCM / FCM in some occasions. However, this should not affect your real users.
We are looking beyond Firebase and working with Play Store team to avoid this inconvenience.
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
add a comment |
from Firebase support:
Hi there,
It seems that this is a known minor issue with our internal infrastructure where the device used for the Play Store review can be BLACKLISTED by GCM / FCM in some occasions. However, this should not affect your real users.
We are looking beyond Firebase and working with Play Store team to avoid this inconvenience.
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
from Firebase support:
Hi there,
It seems that this is a known minor issue with our internal infrastructure where the device used for the Play Store review can be BLACKLISTED by GCM / FCM in some occasions. However, this should not affect your real users.
We are looking beyond Firebase and working with Play Store team to avoid this inconvenience.
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
answered May 7 '18 at 16:08
juan Luisjuan Luis
9111
9111
add a comment |
add a comment |
I can conclude after researching this problem that when an emulator runs the app Firebase will return BLACKLISTED. Also thanks to @kR105
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
2
I saw this morning in my server log that a Nexus 5X sent me a BLACKLISTED token so it seems it can occur to a real device. Strange.
– fralbo
Apr 6 '17 at 6:31
@2ndGAB are you sure it is not an emulated device? Or how can you be sure?
– sj0rske
Apr 6 '17 at 6:33
I cannot be sure at 100%, But that would be surprising that a developper uses my application webservices to make some tests.
– fralbo
Apr 6 '17 at 7:00
I also have a Nexus 5X BLACKLISTED, I am not using an emulator.
– Dieter Donnert
Aug 2 '17 at 17:58
No,I have quite a few user getting BLACKLISTED...
– ken
Oct 18 '17 at 16:49
|
show 4 more comments
I can conclude after researching this problem that when an emulator runs the app Firebase will return BLACKLISTED. Also thanks to @kR105
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
2
I saw this morning in my server log that a Nexus 5X sent me a BLACKLISTED token so it seems it can occur to a real device. Strange.
– fralbo
Apr 6 '17 at 6:31
@2ndGAB are you sure it is not an emulated device? Or how can you be sure?
– sj0rske
Apr 6 '17 at 6:33
I cannot be sure at 100%, But that would be surprising that a developper uses my application webservices to make some tests.
– fralbo
Apr 6 '17 at 7:00
I also have a Nexus 5X BLACKLISTED, I am not using an emulator.
– Dieter Donnert
Aug 2 '17 at 17:58
No,I have quite a few user getting BLACKLISTED...
– ken
Oct 18 '17 at 16:49
|
show 4 more comments
I can conclude after researching this problem that when an emulator runs the app Firebase will return BLACKLISTED. Also thanks to @kR105
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
I can conclude after researching this problem that when an emulator runs the app Firebase will return BLACKLISTED. Also thanks to @kR105
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
answered Mar 20 '17 at 15:45
sj0rskesj0rske
177211
177211
2
I saw this morning in my server log that a Nexus 5X sent me a BLACKLISTED token so it seems it can occur to a real device. Strange.
– fralbo
Apr 6 '17 at 6:31
@2ndGAB are you sure it is not an emulated device? Or how can you be sure?
– sj0rske
Apr 6 '17 at 6:33
I cannot be sure at 100%, But that would be surprising that a developper uses my application webservices to make some tests.
– fralbo
Apr 6 '17 at 7:00
I also have a Nexus 5X BLACKLISTED, I am not using an emulator.
– Dieter Donnert
Aug 2 '17 at 17:58
No,I have quite a few user getting BLACKLISTED...
– ken
Oct 18 '17 at 16:49
|
show 4 more comments
2
I saw this morning in my server log that a Nexus 5X sent me a BLACKLISTED token so it seems it can occur to a real device. Strange.
– fralbo
Apr 6 '17 at 6:31
@2ndGAB are you sure it is not an emulated device? Or how can you be sure?
– sj0rske
Apr 6 '17 at 6:33
I cannot be sure at 100%, But that would be surprising that a developper uses my application webservices to make some tests.
– fralbo
Apr 6 '17 at 7:00
I also have a Nexus 5X BLACKLISTED, I am not using an emulator.
– Dieter Donnert
Aug 2 '17 at 17:58
No,I have quite a few user getting BLACKLISTED...
– ken
Oct 18 '17 at 16:49
2
2
I saw this morning in my server log that a Nexus 5X sent me a BLACKLISTED token so it seems it can occur to a real device. Strange.
– fralbo
Apr 6 '17 at 6:31
I saw this morning in my server log that a Nexus 5X sent me a BLACKLISTED token so it seems it can occur to a real device. Strange.
– fralbo
Apr 6 '17 at 6:31
@2ndGAB are you sure it is not an emulated device? Or how can you be sure?
– sj0rske
Apr 6 '17 at 6:33
@2ndGAB are you sure it is not an emulated device? Or how can you be sure?
– sj0rske
Apr 6 '17 at 6:33
I cannot be sure at 100%, But that would be surprising that a developper uses my application webservices to make some tests.
– fralbo
Apr 6 '17 at 7:00
I cannot be sure at 100%, But that would be surprising that a developper uses my application webservices to make some tests.
– fralbo
Apr 6 '17 at 7:00
I also have a Nexus 5X BLACKLISTED, I am not using an emulator.
– Dieter Donnert
Aug 2 '17 at 17:58
I also have a Nexus 5X BLACKLISTED, I am not using an emulator.
– Dieter Donnert
Aug 2 '17 at 17:58
No,I have quite a few user getting BLACKLISTED...
– ken
Oct 18 '17 at 16:49
No,I have quite a few user getting BLACKLISTED...
– ken
Oct 18 '17 at 16:49
|
show 4 more comments
The App will be running on an emulator hence Firebase token will be Blacklisted
answered Nov 16 '18 at 8:50
RamaRama
1
add a comment |
The App will be running on an emulator hence Firebase token will be Blacklisted
answered Nov 16 '18 at 8:50
RamaRama
1
add a comment |
The App will be running on an emulator hence Firebase token will be Blacklisted
answered Nov 16 '18 at 8:50
RamaRama
1
The App will be running on an emulator hence Firebase token will be Blacklisted
answered Nov 16 '18 at 8:50
RamaRama
1
answered Nov 16 '18 at 8:50
RamaRama
1
answered Nov 16 '18 at 8:50
RamaRama
1
answered Nov 16 '18 at 8:50
RamaRama
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f42136122%2fwhy-does-firebase-push-token-return-blacklisted%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
We have the same problem. Any news about this strange behaviour?
– DreamOfMirrors
Feb 11 '17 at 11:41
@DreamOfMirrors No news :( , still experiencing the same problem.. Did you find a solution?
– sj0rske
Feb 14 '17 at 17:06
1
This just happened to me too, the only thing I can add is that this came from an Android device (My app runs on Android & iOS) and that I read somewhere (can't find where) that this may be related to the app being run on emulators.
– kR105
Feb 20 '17 at 9:06
@kR105 If it happens to be that emulators are blacklisted and when I look at my Firebase statistic I currently have 3 blacklisted devices in my database and 3 foreign country's registered in Firebase that are not related to my app. So these device can be emulators. Still not sure...
– sj0rske
Feb 20 '17 at 22:48