#✅ - Settings for the AndroidManifest.xml (from v4 to v6)

3 messages · Page 1 of 1 (latest)

hybrid osprey
#

Looking to the migration guide for the amplift v5 (React Native), it's possible to see a suggestion to remove the following code block from the AndroidManifest.xml file:

- <service
-   android:name="com.amazonaws.amplify.pushnotification.RNPushNotificationMessagingService"
-   android:exported="false">
-   <intent-filter>
-     <action android:name="com.google.firebase.MESSAGING_EVENT"/>
-   </intent-filter>
- </service>

Although, I have more code in this same file that is related to the com.amazonaws.amplify.pushnotification package, which are:

  • 1 <service> tag containing the android-name equal to com.amazonaws.amplify.pushnotification.RNPushNotificationDeviceIDService;
  • 1 <receiver> tag containing the android-name equal to com.amazonaws.amplify.pushnotification.modules.RNPushNotificationBroadcastReceiver.

Should I remove all these mentioned tags related to the com.amazonaws.amplify.pushnotification or only the specific tag mentioned on the docs?

spice sparrow
#

Hey, @hybrid osprey 👋. Sorry we didn't get you a reply sooner on this, but wanted to see if you're still blocked by this. You should be removing all references to com.amazonaws.amplify.pushnotification from your AndroidManifest.xml file to ensure the push notifications are handled properly.

You may have already figured this out and are unblocked, but wanted to make sure we got you a reply! Let us know if you're still running into issues migrating.

keen bayBOT
#

✅ - Settings for the AndroidManifest.xml (from v4 to v6)