Rich Push Notifications

Overview

Rich Push allows your app to display notifications with enhanced content, such as HTML pages or media, and handle them through a dedicated activity.

Applicable for SDK versions below 7.0.

Implementation Details

1. Configure the Android Manifest

To enable Rich Push functionality, update your app's AndroidManifest.xml with the required intent-filter.

Add the following intent filter to your activity (e.g., MainActivity):

<activity
    android:name=".MainActivity">
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <action android:name="com.mapp.RICH_PUSH" />
        <category android:name="android.intent.category.LAUNCHER" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="${applicationId}" />  //mandatory for Android FCM SDK v6.0.9 and later
    </intent-filter>
</activity>

2. Handle Rich Push Intents in onCreate

In the onCreate() method of the same activity, add the following line to handle incoming Rich Push messages:

Appoxee.handleRichPush(this, getIntent());

3. Handle Updated Intents (e.g., When App is Already Running)

Also, override onNewIntent() in the same activity to ensure Rich Push messages are handled when the app is already open:

@Override
protected void onNewIntent(Intent intent) {
	super.onNewIntent(intent);
	Appoxee.handleRichPush(this,intent);
}

Localized Buttons Behavior
The Engage SDK updates its localization configuration once per day. If the app is installed and opened
before localized buttons are configured in the Mapp Engage interface, it will fetch the current (non-
localized) settings and not update them again for 24 hours.
As a result, notifications—both simple and rich—may display buttons in English instead of the
intended localized language.
Tip: To ensure accurate testing, configure localized buttons in the Mapp Engage interface
before installing or launching the app. Alternatively, reinstall the app or clear its data to
trigger a fresh configuration fetch

Localized Buttons Behavior
The Engage SDK updates its localization configuration once per day. If the app is installed and opened
before localized buttons are configured in the Mapp Engage interface, it will fetch the current (non-
localized) settings and not update them again for 24 hours.
As a result, notifications—both simple and rich—may display buttons in English instead of the
intended localized language.
Tip: To ensure accurate testing, configure localized buttons in the Mapp Engage interface
before installing or launching the app. Alternatively, reinstall the app or clear its data to
trigger a fresh configuration fetch

Localized Buttons Behavior

The Engage SDK updates its localization configuration daily. If the app is installed and opened before localized buttons are configured in the Mapp Engage interface, it will fetch the current (non-localized) settings and not update them again for 24 hours.

As a result, notifications, both simple and rich, may display buttons in English instead of the intended localized language.

Tip:

To ensure accurate testing, configure localized buttons in the Mapp Engage interfacebefore installing or launching the app. Alternatively, reinstall the app or clear its data totrigger a fresh configuration fetch.