If you faced one of these errors:

W/WonderPush.Push.FCM.FCMPushService: The Google Play Services have not been added to the application
    java.lang.ClassNotFoundException: com.google.android.gms.common.GooglePlayServicesUtil
     Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.common.GooglePlayServicesUtil" on path: DexPathList[…]
D/WonderPush.Push: Used push service: (none)

E/WonderPush: Failed to show the notification
    java.lang.IllegalArgumentException: Invalid notification (no valid small icon)

then this update is for you.
Other users are encouraged to update too.

Changelog:

• Fix compatibility with recent Firebase modules

Changelog:

• Small fix to ensure a bad configuration does not prevent any received notification from being displayed due to an invalid small icon resource. If you are impacted then you must upgrade our FCM module to v1.0.2 to fix further issues.

Changelog:

• Fix a ClassNotFoundException when notification opens an external app.

Changelog

This release contains a few bugfixes.

Changelog:

• Change publication to Maven Central OSSRH directly, as BinTray JCenter is going defunct
• Fix NPE on setUserId() called quickly after first startup
• Support for collapsible big pictures
• Miscellaneous

As JCenter is sunsetting, please ensure that you include the Maven Central repository in your build configuration. Open your root build.gradle:

allprojects {
    repositories {
        // Make sure the following line is present
        mavenCentral()
    }
}

From this version forward, we will no longer publish to JCenter.

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.

WonderPush launches in-app messaging for apps… and websites!

In-apps are messages that appear on top of mobile apps to drive engagement. Now, WonderPush has made them available to websites as well!

Starting today, WonderPush is launching a brand new in-app messaging feature that will let marketing and content teams produce targeted, contextual and customizable messages that work just as well on your website and your mobile applications, without any coding.

Without code or help from your technical team, you can create and remotely trigger the display of banners, modals and alerts targeting users as they browse your site and use your app, letting you engage them in a specific action.

Read more on our blog post.

How to use in-app messaging

https://docs.wonderpush.com/docs/in-apps-for-websites
https://docs.wonderpush.com/docs/in-apps-for-mobile-apps

Changelog:

• Upgrade to iOS SDK v4.0.1

Changelog:

• Using iOS SDK v4.0.1

Changelog:

• Using iOS SDK v4.0.1

Changelog:

• Fixed a potential race condition