I have seen a few of these in the past few days
As you can see, on the preA/pre rows, the device starts with prenull;/pre
Is this a bug ?
Hello,
Could you please share your app and database. Also please tell their names and steps to test.
What devices do you have? Please tell their Android versions.
The database is already shared and its called urVoice 3.
Android versions I only know one, as the rest are users, which is 4.1.2
There are no steps, the second the a user downloads the app and open it, the device is registered. These did not happen before, so is unlikely to be my end, but you never know
Sure. Thanks. We will test and let you know the result.
Is your app shares with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a as well?
Hello Addy,
Could you please tell us the name of your app (if it's shared with us)?
The app is shared and also called urVoice.
Hi Addy,
This is an expected behaviour. Device ID beginning with null is not a problem.
The only issue we see here is an undefined token. Most probably you didn't set (or set incorrectly) Sender ID and API Key.
If its a null, the notifications will not be directed to the correct device ? If I send a PN then my iPhone gets it, but my Android does not. Hence why I checked and found it was null ?
Hi Addy,
Please delete all items with "undefined" value in the token field.
See details http://prntscr.com/4ej9s4/direct
And then try to test again.
Also you don't need to wary about "null;.." in device id.
Regards.