3 ms·
One group of developers this is going to affect most are those who used Parse's GCM Server Key for push notifications. Since Parse is probably not going to rev
by gdeglin 11y ago
One group of developers this is going to affect most are those who used Parse's GCM Server Key for push notifications.
Since Parse is probably not going to reveal this key, Android developers using Parse for push will not be able to use their existing GCM push tokens with other services.
- dozy 11y agoParse authenticates with GCM using the API key that you provide, as do all other services AFAIK. So, all developers need to do is use that same key in their new push provider, and their push tokens will work. The tricky part is actually making sure that all of your push tokens that are in the Parse database are migrated to the push provider that you've chosen. EDIT: I stand corrected, looks like you have the option to use their key as you said, my apologies! Should have figured the founder of OneSignal would know ;-)
- simscitizen 11y agoThe easiest way to deal with this is to add your sender ID to the app manifest, so Parse registers with both its sender ID and yours: https://parse.com/docs/android/guide#push-notifications-setting-up-push https://parse.com/docs/android/guide#push-notifications-sett... This requires a new release of your app, but that is a necessity in any case.
- gdeglin 11y agoYou're right, it seems like this should work.
- rpgmaker 11y agoAnd here I was thinking that because Parse was acquired by facebook using their Push notifications offering was as safe bet as I could make. Can anyone recommend an alternative short of implementing my own GCM server app?