Changelog:

  • Automatically adding client ID/SECRET to the notification service extension file

Changelog v3.0.0:

  • This version officially releases in-app messaging!
  • Attribute events to the last clicked notification. Lets you view events generated by a particular notification in your dashboard.
  • Count delivered notifications and report it to your dashboard.
  • Detect devices that no longer receive notifications
  • Segment users depending on app usage and real-time presence.
  • Reduce number of network calls
  • Fix spurious "App Open" events tracked on some background activities
  • For better privacy, WonderPush no longer collects events from non-subscribers. If you think you have a use-case that would justify collecting data for non-subscribers, please contact us.

Breaking changes:

  • Removed isReady() . You do not need to wait to use WonderPush.

We no longer depend on Firebase Messaging by default, you must make sure to add the wonderpush-cordova-sdk-fcm plugin.

Upgrading:

Follow our upgrade guide.

Changelog:

  • Remove dependency on androidx.appcompat:appcompat
  • Forgot to raise minSdkVersion to 21 because of okhttp3
  • Fix tracking logic for @INAPP_VIEWED and @INAPP_CLICKED

Do not forget to look at v4.0.0 changelog and breaking changes.

Version 4 brings you:

  • In-app messaging
  • Attribute events to the last clicked notification. Lets you view events generated by a particular notification in your dashboard.
  • Count delivered notifications and report it to your dashboard.
  • Detect devices that no longer receive notifications
  • Segment users depending on app usage and real-time presence.
  • Drop com.loopj.android:android-async-http:1.4.9 in favor of com.squareup.okhttp3:okhttp:3.14.9
  • Reduce number of network calls
  • Fix spurious "App Open" events tracked on some background activities
  • For better privacy, WonderPush no longer collects events from non-subscribers. If you think you have a use-case that would justify collecting data for non-subscribers, please contact us.

Upgrading:

Follow our upgrade guide.

Changelog:

  • This version officially releases in-app messaging!
  • Attribute events to the last clicked notification. Lets you view events generated by a particular notification in your dashboard.
  • Count delivered notifications and report it to your dashboard.
  • Detect devices that no longer receive notifications
  • Segment users depending on app usage and real-time presence.
  • Reduced logging verbosity
  • Added a warning when method swizzling is detected. It's potentially incompatible with WonderPush.setupDelegate(for:)
  • Fix spurious "App Open" events tracked on some background activities
  • For better privacy, WonderPush no longer collects events from non-subscribers. If you think you have a use-case that would justify collecting data for non-subscribers, please contact us.

Breaking changes:

  • Removed isReady: and WP_NOTIFICATION_INITIALIZED NSNotification. You do not need to wait to use WonderPush.
  • You must now initialize the SDK using the clientId / clientSecret credentials from the NotificationServiceExtension .

Upgrading:

Follow our upgrade guide.

GitHub release
Integration guide
Upgrading to v3 guide

Changelog:

TL;DR: You can now support Huawei push notifications and you don't need to change your setup if you're not interested in it.

Please follow our Huawei integration guide to get started.

  • This version adds optional support for HCM, aka Huawei Push Kit.
  • FCM support, aka Firebase Cloud Messaging (previously GCM) is now modular and can be removed from your project's dependencies explicitly using some Gradle kung fu.
    The main SDK library depends on it so that you don't need to update your integration.

In 2011 SSL v2 was deprecated, followed in 2014 by SSL v3 due to irreparable security flaws.
In 2018 TLS v1.0 and TLS v1.1 have been scheduled for deprecation by Apple, Google, Microsoft, and Mozilla for March 2020.
This leaves us with TLS v1.2 which is already 12 years old, and the latest member of the family, TLS v1.3, which is now 2 years old.
Security is important for us and we’re following the best practices to keep you protected.

Starting 2020-06-17 at 12:00 UTC, we have hence dropped support for the deprecated TLS v1.0 and TLS v1.1 protocols as well as the insecure RSA cypher suites, to support only TLS v1.2 and TLS v1.3 with ECDHE cypher suites.

For the unlucky few that use an outdated setup, take the opportunity to finally upgrade it to this shiny new version you’ve been dreaming for month.
If for whatever reason you happen to be impacted, do not hesitate to contact us using the chat and we’ll work out a solution together. Using a local proxy server that can upgrade your connection without disruption is usually the fastest solution; sometimes you only need a few extra lines of code to explicitly activate existing but disabled TLS v1.2 support in your old SSL library.

Upgrading:

Make sure you can use Java 8 language features.
See corresponding Android documentation

android {
  // Configure only for each module that uses Java 8
  // language features (either in its source code or
  // through dependencies).
  compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
  }
  // For Kotlin projects
  kotlinOptions {
    jvmTarget = "1.8"
  }
}

Changelog:

  • In-app messaging private beta. Contact us to get in!
  • Bug fixes