Changelog:

  • Declare missing exported attribute for Android 12 compatibility

This update is required if your application uses targetSdk 31.
This releases fixes the following build error:

Manifest merger failed : Apps targeting Android 12 and higher are required
to specify an explicit value for android:exported when the corresponding
component has an intent filter defined.

See the related Android 12 change.

If you use "targetSdk 31" this SDK version isrequired, 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:

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.

Changelog:

  • Declare missing exported attribute for Android 12 compatibility

This update is required if your application uses targetSdk 31.
This releases fixes the following build error:

Manifest merger failed : Apps targeting Android 12 and higher are required
to specify an explicit value for android:exported when the corresponding
component has an intent filter defined.

See the related Android 12 change.

If you are facing a Google Play application submission rejection with the cause "Remediation for Implicit PendingIntent Vulnerability", this update is for you.
No customer have currently faced this, considering we were already implementing many best practices, but there was a few more we could take advantage of, which we did in this release.

Changelog:

  • Avoid implicit PendingIntents

If your application is submitted to Google Play with the HCM module included, your application may be rejected by the new app release verification rules, mentioning the cause "Remediation for Implicit PendingIntent Vulnerability".

Simply update our HCM module and you should be good to go.

Changelog:

  • Update Huawei Push Kit to v5.3.0.304:
    • Remediation for Implicit PendingIntent Vulnerability

Changelog:

  • use iOS SDK v4.0.4:
    • bug fixes
  • use Android SDK v4.0.7:
    • Upgrade the last dependencies still using pre-AndroidX support libraries. Without this change you needed to use android.enableJetifier=true.
    • Use compileSdkVersion 30 and get rid of deprecated classes and method calls.
    • Multiple StrictMode violation fixes.
    • The SDK can now be imported in your own project as a project dependency without altering its build.gradle files. This makes it easier to hack it and contribute back to the community.