If you use "targetSdk 31" this SDK version is required, along with our FCM module v1.0.4 minimum.
For the others, we recommend to always use the latest published version.

Changelog:

• Support targeting builds to Android 12, when using targetSdk 31
• Support delaying on launch/foreground in-apps on identified custom splash or routing activities
• Change the APP_LAUNCH in-app system trigger to match application cold starts
• Allow to display in-apps contained in manually-displayed data push notifications

Android 12 support

If you use targetSdk 31, this SDK version is required.
You will also need to upgrade the version of our FCM module to v1.0.4 minimum.

Here is a more detailed outline of the changes:

• Adapt to the Notification trampoline restrictions
• Remove now-unnecessary and now-restricted use of the ACTION_CLOSE_SYSTEM_DIALOGS intent.
• Fix missing @APP_OPEN events when an activity is resumed after a long time, like Android 12 now does when pressing back on the root activity.
• Handle a few deprecations

Support delaying on launch/foreground in-apps on identified custom splash or routing activities

If your application uses a custom splash activity, or a routing activtiy to resolve deeplinks using application code, to avoid triggering an in-app shown on app launch or app foreground, you can now mark those activities with the following metadata in your AndroidManifest.xml, inside their <activity> tag:

<meta-data android:name="com.wonderpush.sdk.iam.ignoreForeground" android:value="true" />

Note that Android 12 now proposes a convenient API for handling splash screens.
It also adds splash screens automatically to all loading applications, so if you have a custom splash screen activity you should probably migrate your existing splash screen.