C2DM shutdown - what happens if still using C2DM API for GCM?

Question

The long-deprecated Google C2DM push messaging service is being completely shut down as of October 20, 2015. Does anyone know what will happen in this legacy app scenario?

• Our app server migrated to GCM several years ago
• Our Android app switched to use the GCM sender ID at the same time
• Over 99% of our users are migrated to GCM
• However... our Android app still uses the C2DM API internally
  • The <receiver> is a C2DMBroadcastReceiver/BroadcastReceiver, not a GcmReceiver
  • The <service> is a subclass of C2DMBaseReceiver/IntentService, not GcmListenerService.

So, while this has been working for GCM to date, I'm concerned about what will happen on October 20. Will our app still receive GCM messages using the C2DM API? I believe it will and that we're OK, but I'd like to be sure.

Of course, we need to complete the migration and update the client code to use the GCM API, and we'll do so. I'm trying to understand the impact for users who don't update the app to receive this fix.

Answer 1

As of Nov 7, 2015 (2.5 weeks after the C2DM shutdown), our app is still able to process GCM messages using the C2DM API. So, that appears to answer my question. Thanks for the input.