Changelog:

  • Fix NPE when no targetUrl was given in the push notification using the API
  • Add missing try/catch in WonderPushNotificationTrackingReceiver
  • Give clicked button index in intent

Changelog:

  • Upgrade to WonderPush Android SDK v4.1.1
    • Avoid <provider android:name="androidx.core.content.FileProvider"> conflicts by using a custom class name.
      This avoids a conflict with Ionic Capacitor projects, and probably with some client apps as well considering the official documentation says:

      Set the `android:name` attribute to `androidx.core.content.FileProvider`.

If you do not use Ionic Capacitor or did not get such a conflict, you can skip this release.

Changelog:

  • Avoid <provider android:name="androidx.core.content.FileProvider"> conflicts by using a custom class name.
    This avoids a conflict with Ionic Capacitor projects, and probably with some client apps as well considering the official documentation says:
      Set the `android:name` attribute to `androidx.core.content.FileProvider`.

If you did not get such a conflict, you can skip this release.
Ionic Capacitor projects will now be able to depend on the WonderPush Android SDK without modifying the generated AndroidManifest.xml.

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:

  • Upgrade to WonderPush Android SDK v4.1.0
    • Support targeting builds to Android 12, when using targetSdk 31
    • 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:

Changelog:

  • Update to WonderPush Android SDK FCM module v1.0.4:
    • 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.5 minimum.
For the others, we recommend to always use the latest published version.

Changelog:

  • Upgrade to WonderPush Android SDK v4.1.0
    • Support targeting builds to Android 12, when using targetSdk 31
    • 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.5 minimum.

Here is a more detailed outline of the changes:

Changelog:

  • Update to WonderPush Android SDK FCM module v1.0.4:
    • 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:

  • Upgrade to WonderPush Android SDK v4.1.0
    • Support targeting builds to Android 12, when using targetSdk 31
    • 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: