Android Push notifications not working in 7.3

This is for users who are currently running Verivo 7.3 and created a google push account before June 26, 2012.  This date is important because this is the date that google deprecated their existing cloud to device messaging framework and replaced with Google Cloud Messaging for Android.

 

If you have configured push and are finding that your android users are not receiving any of the pushes the most likely cause is that the push device token for that user does not exist.  The push device token is a token that the google serves pass down to your device when you first load and app and click ‘Yes’ to accept push notifications.  After that, before your device can receive a push it needs to pass up the token to the google cloud to verify you should receive a push.

 

To verify that a user has a push device token you need to run this query on the Verivo database

select AppID, UserID, PushDeviceToken from tmpcfg_UserAppReltn

 

Push device token is the field that needs to be populated for that user and for the appid they are connecting to.  Having a push token in appid 1000 will not help appid 1001.  If no android users have push tokens but iphone users do there is a specific reason.  The verivo field size for the push device token is varchar(200) by default.  Google changed the size of their token to be up to 4000 characters early 2012.  If you have Verivo 7.4 you are already setup to handle this.  If you have 7.3 you need to modify the tmpcfg_UserAppReltn table

 

ALTER TABLE tmpcfg_userappreltn

Alter Column PushDeviceToken varchar(max) NULL

 

There is no requirement to back up the data or delete anything, you can do this whenever.

 

Now, let’s talk about what happens after this change.  Regrettably, application studio does not like when you change the schema.  We have warnings about changing the schema or direct database inserts for a reason.  What happens in this case is that application studio loses the ability to connect to the user tables when you try to manage users.  If you auto-enroll your users this isn’t a problem.  If you do not use auto enroll, if you do management of workflows or use certain connection value parameters you will have to do all of that work through SQL update and insert commands.  For some you may have to decide what is more important, android push or user maintenance. 

 

Our suggestion would be to install 7.4

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk