Custom FCM and HMS Implementations
If your platform uses a custom FirebaseMessagingService or HmsMessageService, you need to update your AndroidManifest.xml file to avoid service conflicts with Netmera.
Step 1. Manifest Configuration
For Custom FirebaseMessagingService:
FirebaseMessagingService:If you are using your own FirebaseMessagingService class, make sure to add the following line to your AndroidManifest.xml to remove Netmera's default FCM service:
<service
android:name="com.netmera.nmfcm.NMFirebaseService"
tools:node="remove" />For Custom HmsMessageService:
HmsMessageService:If you are using your own HmsMessageService class, include the following entry in your manifest to remove Netmera’s default HMS service:
<service
android:name="com.netmera.nmhms.NMHuaweiService"
tools:node="remove" />Step 2. FCM and HMS Implementations
Deprecated Methods (Before v4.0.12)
The following method is deprecated as of Netmera SDK v4.0.12 and must not be used in new implementations:
Deprecated:
Netmera.isNetmeraRemoteMessage(remoteMessage)Use instead:
Netmera.isNetmeraRemoteMessage(remoteMessage.data)for FCMNetmera.isNetmeraRemoteMessage(remoteMessage.dataOfMap)for HMS
Make sure your codebase reflects these updated signatures to avoid compatibility issues with Netmera push handling.
For Custom FirebaseCloudMesssaging (FCM)
FirebaseCloudMesssaging (FCM)For Custom HmsMessageService (HMS):
HmsMessageService (HMS):Handling Token Updates
You must also report HMS push tokens to Netmera:
Last updated
Was this helpful?