Reputation: 78815
We are using Parse.com to send push notifications. With the announced shutdown, we're now looking into how to migrate to another service. On Android, we haven't configured any GCM sender ID so we have been implicitly using Parse.com's sender ID. That's a problem for the migration (see Urgent note for Parse Android Push users and Migrating an Existing Parse App (section Exporting GCM Registration IDs)).
Therefore, we are now preparing a new version of our Android app with our own GCM sender ID. Is there any way in Parse.com to verify which devices (installation) are associated with our sender ID? How can we check if our update was successful? Does Google provide any API for directly or indirectly checking if a sender ID works with our Google project?
Any tool or any approach that involves writing some code is ok.
Upvotes: 4
Views: 2939
Reputation: 12618
Thanks for posting this question. I help work on OneSignal and I've updated the mentioned blog post based on the feedback.
The blog post now instructs users to also update their ParseInstallation to set their GCMSenderId, as follows:
final ParseInstallation parseInstallation = ParseInstallation.getCurrentInstallation();
parseInstallation.put("GCMSenderId",YOUR_NEW_SENDER_ID);
parseInstallation.saveInBackground();`
This will allow you to track which users are now subscribed with the new GCM Sender ID. It will also tell our Parse importing tools like ours that these subscribed devices can be imported and used.
Upvotes: 2
Reputation: 316
You can find information regarding sending and receiving push notifications from our guide: https://parse.com/docs/android/guide#push-notifications
In particular
...an advanced feature for developers that want to send pushes from multiple push providers, Parse allows you to optionally register your app for pushes with additional GCM sender IDs. To do this, specify the additional GCM sender ID with the following <meta-data>
tag as a child of the <application>
element in your app's AndroidManifest.xml...
and
GCMSenderId: This field only has meaning for Android ParseInstallations that use the GCM push type. It is reserved for directing Parse to send pushes to this installation with an alternate GCM sender ID. This field should generally not be set unless you are uploading installation data from another push provider. If you set this field, then you must set the GCM API key corresponding to this GCM sender ID in your Parse application's push settings.
Upvotes: 0
Reputation: 9258
The open source Parse Server project does not currently support push notifications, but it is in the roadmap and should be available shortly.
If you wish to migrate your Parse Push app to another GCM provider, you will want to update your Android Manifest file with your own GCM Sender Id. Once the app has been deployed to the Google Play store, clients that update to the latest version of your app will register using your GCM Sender Id as well.
You will want to track how many of your active users have updated to the new version of the app to get a better idea of how well your migration is progressing.
The Parse Installation object automatically tracks the client-side app version number. A quick and easy way of determining how many clients have updated your app to the new version of your app is to filter for Installation objects running the new appVersion
or newer.
You should, of course, make sure the updated version of your app has registered with GCM using your new Sender Id properly before you release the new version on the Google Play store. The Android Documentation on Cloud Messaging covers best practices for this. If your app has been configured correctly, you should be able to deliver push notifications to the updated clients using your new push notifications provider.
Upvotes: 0