Questions on GCM -> FCM migration

My company is migrating its Android apps from GCM -> FCM. Following UA's & Google's guides, everything is working as expected. However, we have vestiges of our old UA GCM code remaining, I'd like confirmation that removing the following will have no ill effects. I've been unable to locate references to the following in UA's migration documentation:

  1. Our UA/GCM code included CoreReceiver in our Manifest, it looks like this can be safely removed:

    <receiver android:name="com.urbanairship.CoreReceiver" android:exported="false">
    <intent-filter android:priority="-999">
    <action android:name="com.urbanairship.push.OPENED"/>
    <category android:name="***"/>

  2. We are referencing PlayServicesErrorActivity in our Manifest; we also have an old reference to CoreActivity. Can the reference to CoreActivity be removed while retaining PlayServicesErrorActivity?

    <activity android:name="com.urbanairship.CoreActivity"/>

  3. We have an old reference to ActionService in our Manifest, but it is my understanding that this is not needed if we are not using any Action Situations or custom Actions in our app:

    <service android:name="com.urbanairship.actions.ActionService"/>

Didn't find what you were looking for?

New post


1 comment

  • Hello Craig!

    This is Mikey with Urban Airship; Thanks for posting your questions. 

    If you've migrated over on our latest SDK from GCM to FCM, you should be able to remove what you've mentioned above as long as you're following the appropriate guide to facilitate the migration. You can also verify the requirements needed using our sample app manifest for reference.

    If you're migrating and on an older SDK, it's recommended that you update to ensure that there aren't any unexpected mishaps in the migration process. 


    Mikey R. | Portland, OR

    Comment actions Permalink

Please sign in to leave a comment.