I've got some Android pushtokens that say BLACKLISTED

Comments

21 comments

  • Avatar
    Rob Willett

    Just to add some more information, our apps are working well and have been for over a year, so we're puzzled by this. Its not clear when the pushtoken became BLACKLISTED.

  • Avatar
    Ivan Skoritzky

    Hello Rob,

    Actually, I have found this question on stackoverflow https://stackoverflow.com/questions/42136122/why-does-firebase-push-token-return-blacklisted. And it seems to be that blacklisted tokens occur due to emulators.

    I will try to confirm this conjecture with our developers and I`ll let you know about the results!

    Regards, Ivan

  • Avatar
    Rob Willett

    Ivan,

    Thanks we have already seen that posting, this is not an emulator problem as the only people who use emulators is us and we know exactly what and when we are doing it.

    Rob

  • Avatar
    Ivan Skoritzky

    Rob,

    Could you please let me know the name of the application in question? I want to find and check this device in our user base.

    Regards, Ivan

  • Avatar
    Ivan Skoritzky

    Rob,

    Please let me follow-up on my previous message.

    I have found this device in your userbase. It is Nexus 5X. Actually, it is quite strange because I have seen once the blacklisted token and it was also Nexus 5X. Moreover, as you can see from the stackoverflow thread there were also Nexuses 5X.

    I assume that the issue is in the device model. We will make some test tomorrow with the equal device and I will let you know about the results!

    Regards, Ivan

  • Avatar
    Rob Willett

    Ivan,

    There are two apps in question "Jambuster Production" and "Jambuster Blackwall Tunnel Production".

    We've just looked again at the database we keep of usage and can see that some of the devices in question, all Android devices, used our app 12079 secs ago, thats three hours ago. We don't have any emulators running at the moment, the only emulator we use is Genymotion and thats not running at all.

    I can provide more information as needed but we're struggling to understand why this is happening. Clearly there is a problem, what we have done is update our system to avoid anybody who has a Pushwoosh token of 'BLACKLISTED" which should help us a little.

    Any suggestions welcomed.

    Rob

  • Avatar
    Rob Willett

    Ivan,

    Ah! Thats interesting. We don't own a real Nexus 5X and from memory we don't use a 5X in any of our emulators.

    A puzzle! Do ypu log Android versions as well? That might assist us.

    Rob

  • Avatar
    Ivan Skoritzky

    Rob,

    The Android version is 6.0.1 for both devices.

    Regards, Ivan

  • Avatar
    Rob Willett

    Thats a coincidence.

    You only have two devices blacklisted? We can see a lot more in our records. We deleted very old ones, but we can see 22 different devices so we have had significantly more.

    Rob

  • Avatar
    Ivan Skoritzky

    Hello Rob,

    Actually, yes, I have downloaded the full user bases of these two apps and I have found only 2 devices blacklisted (one on each app). Probably, other devices were invalidated and removed from our database.

    Also, I have tested physical device Nexus 5X, and it works as expected.

    By the way, Nexus 5X is one of two devices with Google Play access in Android Studio Virtual Device Manager (the second one is Nexus 5).

    I have emulated Nexus 5X with Android 8.0 and it works fine, registered correctly and receive pushes.

    Unfortunately, I could not emulate it on Android 6.0 because it would not have access to Google Play Store. And I cannot debug without it. We can build our own sample and test in on 6.0, but it will take some time.

    However, I will pass this information to our developers in order to find out why such devices appear.

    Regards, Ivan

  • Avatar
    Rob Willett

    Ivan,

    Thanks for the update. It's a mystery to us as we know the devices in question are not emulators. We have had a lot, certainly well over 30 in our records.

    We're going to update our monitoring to

    1) Get it actually working :) 2) Add in code to check for BLACKLISTED as devices register on our servers. At least then we have a fighting chance to see whats going on.

    Be interested in any results you find from your side.

    Thanks

    Rob

  • Avatar
    Rob Willett

    Ivan,

    We use Genymotion for Android Emulation and just about every version has access to the Google Play Store using Gapps. The latest version of Genymotion now has the ability to download these Gapps from within the application itself. It just makes it simpler to run them, but its very nice.

    We never use the 'standard' Android emulator as it was so slow on a top of the range Mac with 32GB, SSD and dual fast graphics cards :)

    As far as we can see, we don't have a problem with your PushWoosh software and the Android emulators. We do test that the emulators work and so far no issues that we know about. We don't think the emulators are the issue per se.

    Rob

  • Avatar
    Ivan Skoritzky

    Rob,

    The thing is that we receive such tokens from Google but the reason is undefined yet. If we find the valid information for this issue I will update this conversation.

    Regards, Ivan

  • Avatar
    Rob Willett

    Ivan,

    Thanks.

    Thats worrying that Google is sending you BLACKLISTED tokens that you haven't seen before. We now simply ignore anything that has the BLACKLISTED token so it doesn't cause us any problems.

    We did think that this was due to devices not responding to a push notification but we can see that some devices are responding, so that rules that out.

    Can this be for rooted Android devices? We don't root at all and never have so its not easy to test. I wonder if we can root a Genymotion device to see if that causes the problem?

    Any update welcomed if you get anything. I'm surprised Google can't tell you.

    Rob

  • Avatar
    Ivan Skoritzky

    Rob,

    Actually, I still have not received the answer from Google. Maybe they will clarify.

    But I have found another thread https://github.com/firebase/quickstart-android/issues/212

    "We had that issue for a while and then it stopped. The issue is from Google's servers and shouldn't have anything to do with you've implemented Firebase in your application. We didn't get any solid answers from Google when we had this issue but it randomly started and stopped after a few days."

    So, I'm not very optimistic that we will receive the clear answer.

    Regards, Ivan

  • Avatar
    Rob Willett

    Ivan,

    Thanks for this. We hadn't seen that thread.

    I have to say thats quite worrying that Firebase can issue tokens like 'BLACKLISTED' and Google can't explain it. Thats pretty poor from Google. Also the word BLACKLISTED is quite a specific word, to us it means that Google has explicitly stopped something rather than using words like INVALID_TOKEN or whatever.

    I note as well that this was a Nexus 5x that had the problem. I'm wondering if this was a specific issue with Nexus 5X and some firmware issue on them. We don't own a Nexus 5X so we have never noticed it.

    We've updated our code so that we don't send anything to anybody thats got this token and our code will automatically update if and when they get a new valid token from Firebase.

    We'll get a dump of all the ID's that have BLACKLISTED and see if they change.

    Thanks for the help,

    Rob

  • Avatar
    Ivan Skoritzky

    Rob,

    Glad to hear that the issue is resolved on your side!

    Seems to be that device model "Nexus 5x" is set by default when the token is blacklisted and it has no connection with a real device, the thing is that on different accounts the device is the same. And other Tags is equal for these devices, such as "OS Version”:“6.0.1.0”,“Country”:“us”,“City”:“us, mountain view”.

    Ivan

  • Avatar
    Rob Willett

    Ivan,

    We haven't fixed the issue just stopped the issue becoming a problem :)

    Rob

  • Avatar
    Ivan Skoritzky

    Rob,

    Yes, I understand :) I hope we will find the core of the issue.

    Regards, Ivan

  • Avatar
    Ivan Skoritzky

    Hi Rob!

    I have just received the response from Firebase support:

    "Please note that Google blacklists some devices that have bad behavior. These are mainly emulators and fake devices used to test thousands of applications.

    In case you are experiencing this issue with end user devices, could you please provide a sample registration token of the affected device?"

    Not very helpful since you are sure that these devices cannot be emulators. And we cannot provide any token because the value is "BLACKLISTED". Don`t you have the previous token values for these devices?

    Regards, Ivan

  • Avatar
    Rob Willett

    Ivan,

    Thanks. We haven't seen any issues whatsoever with emulators, we only use the Genymotion emulators and they've been fine (AFAIK). Not sure what a fake device is though.

    As you say, we can't provide tokens as the token simply says BLACKLISTED. We don't have an easy way to get previous tokens either as we don't backup that information.

    The easiest thing we could do is do a daily backup just of the SQL table we use that stores the notification tokens and then try and compare what happens over time. Not convinced that will make a massive difference, but we'll try and put a new script in over the weekend

    Rob

Please sign in to leave a comment.