If your Android application uses Pushwoosh alongside another service that relies on Firebase Cloud Messaging (FCM), a conflict can occur. Both services may try to handle the incoming push notification, but only one will succeed. This can prevent Pushwoosh notifications from being displayed, even if the device is registered correctly.
To resolve this, you need to set a higher priority for the Pushwoosh service in your AndroidManifest.xml file. This ensures that Pushwoosh receives and processes the notification payload first.
How to set the service priority:
- Open your project's
AndroidManifest.xmlfile. - Locate the
<service>declaration forcom.pushwoosh.firebase.PushwooshFcmHelperService. - Add an
<intent-filter>with apriorityattribute inside the service tag. Setting a higher value, such as100, gives it priority over other services with default or lower priority values.
Here is an example of the correct configuration:
<service
android:name="com.pushwoosh.firebase.PushwooshFcmHelperService"
android:exported="false">
<intent-filter android:priority="100">
<action android:name="com.google.firebase.MESSAGING_EVENT" />
</intent-filter>
</service>
After adding this configuration and rebuilding your app, Pushwoosh will be able to correctly process and display notifications.
Comments
0 comments
Please sign in to leave a comment.