-
April 25th, 2018, 07:32 AM
#1
This changes the scenario completely. If you are experiencing the problem only on some devices, it may be due to how the device token is obtained. Let me explain.
As per Google’s suggested practices, if the package version of the app doesn’t change, our Android client library skips requesting a device token and reuses the last one it obtained (which is always saved on the SharedPreferences). So, the error may be due to some of your devices still using a token obtained with the previous sender ID.
If this is the case, uninstalling and reinstalling the app on those devices will force our client library to request a new token and should fix the problem.
Let me know if this is of help.
Similar Threads
-
By kgstefan88 in forum Client SDKs
Replies: 2
Last Post: October 19th, 2017, 01:54 PM
-
By MattStone in forum Client SDKs
Replies: 2
Last Post: September 8th, 2016, 04:53 AM
-
By CitiMan in forum Client SDKs
Replies: 2
Last Post: November 21st, 2006, 01:55 PM
-
By Mone in forum Client SDKs
Replies: 0
Last Post: November 9th, 2006, 04:12 PM
-
By Mone in forum Client SDKs
Replies: 0
Last Post: November 7th, 2006, 11:24 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 02:28 PM.
Bookmarks