5.6.0

Channels: current

🚀 New Features

• feat: 🎉 introduces Custom Events Support for the Android SDK. To get started with using Custom Events, please contact support@onesignal.com to enable this feature for your app. Please see documentation on Custom Events.

✨ Improvements

• feat: IAMs now display when triggers added before first fetch (#2528)

🐛 Bug Fixes

• fix: end initialization early if device storage is locked (#2520)

📦 Version

5.6.0

---

This change is 

5.5.0-beta

Channels: beta

🔖 Auto-Generated Release Notes

Channels: beta

🚀 New Features

• feature: Exposing accessors thru suspend (#2502)

🐛 Bug Fixes

• fix: a rare NPE from PermissionViewModel introduced in 5.4.0 (#2504)
• fix: NPE in SyncJobService since 5.4 (#2500)
• fix: Rare User and Subscription creates and updates processing out of order (introduced in 5.4.0) (#2419)
• fix: Remove throwing "initWithContext was not called or timed out", introduced in 5.4.0 (#2408)

🔧 Improvements

• Improvement: failure message shows that appID is missing (#2506)
• improvement: Offloaded work on background threads. (#2394)

📦 Version

5.5.0-beta

---

This change is 

5.4.2

Channels: current

🔖 Auto-Generated Release Notes

Channels: current

🚀 New Features

• feat: Enable docs (#2507)

🐛 Bug Fixes

• bug: catch exception if opening a notification fails (#2508)
• fix: IAM with NOT_EQUAL_TO trigger always shows up (#2509)
• fix: NPE when setting timezone on app focus (#2505)
• fix: send receive receipt even when preventDefault is called (#2512)

🔧 Improvements

• chore: Kotlin 1.9 update (#2403)
• chore: Bump firebase-messaging to 24.0.0 (#2149)

📦 Version

5.4.2

---

This change is 

5.4.1

Channels: current

Summary

This rollbacks all changes introduced in 5.4.0.

• This version same as 5.1.38

In the coming weeks, a 5.4.2 release will be made containing the 5.4.0 improvements again plus fixes for all outstanding 5.4.0 issues.

📦 Version

5.4.1

5.4.0

Channels: current

⚠️ NOTE: This version is not recommend. Please use 5.4.1 or newer instead. ⚠️

🔖 Auto-Generated Release Notes

Channels: current

What is NOT included

If you use one these features you will need to stay the matching version:

• 5.2.x - Identity Verification (JWT) - Feature is still in beta
• 5.3.x - Custom Outcomes - Feature is still in beta

🔧 Improvements

• improvement: Offloaded work on background threads. (#2394)
• improvement: Using a OneSignal Threadpool to execute all OneSignal related operations
• improvement: Added newer suspend methods that could be used in ViewModels to init the SDK, login and logout
• improvement: Improved code quality around PermissionsActivity.

🚀 New Features

• Feat: Detect for timezone changes and update the user (#2378)
• add: security hardening around webview javaScriptEnabled (#2377)

🐛 Bug Fixes

• Fix: ANR on POST to Outcomes endpoint (#2371)
• ANR GmsLocationController timing out ([#2396]#2396)
• ANR #2335
• ANR #2266
• ANR #2397
• ANR #2399
• ANR #2400
• Crash/ANR #2192

📦 Version

5.4.0

Upgrade Notes

This version solves ANRs from initWithContext, however if your app calls OneSignal accessors (ex. OneSignal.User.oneSignalID) on the main thread immediately after initWithContext you may see the ANR problem shift to them. To solve all OneSignal ANRs, we recommend moving all OneSignal accessor calls off the main thread.

---

This change is 

5.4.0-alpha-03

Channels: alpha

🚀 New Features

• Feat: Detect for timezone changes and update the user (#2378)

🐛 Bug Fixes

• Fix: ANR on POST to Outcomes endpoint (#2371)

🔧 Improvements

• add: security hardening around webview javaScriptEnabled (#2377)

📦 Version

5.4.0-alpha-03

---

This change is 

5.1.38

Channels: stable

🚀 New Features

• Feat: Detect for timezone changes and update the user (#2378)

🐛 Bug Fixes

• Fix: ANR on POST to Outcomes endpoint (#2371)

🔧 Improvements

• add: security hardening around webview javaScriptEnabled (#2377)

📦 Version

5.1.38

---

This change is 

5.4.0-alpha-02

Channels: alpha

🔖 Auto-Generated Release Notes

Channels: alpha

🚀 New Features

• feat: Add Kotlin MainApplication and suspend initialization support (#2374)

🐛 Bug Fixes

🔧 Improvements

📝 Uncategorized PRs

📦 Version

5.4.0-alpha-02

---

This change is 

5.4.0-alpha-01

Channels: Alpha

Highlights

• Non-blocking initialization

  • OneSignal.initWithContext has been refactored so heavy disk and network work are moved off the main thread. ANRs related to initialization should now be effectively eliminated when the SDK is used in the recommended way (see Notes below).

• Performance Improvements

  • In our testing, the time spent on the main thread during initialization dropped by ~80% (e.g., from ~47–49 ms down to ~8 ms on a cold start in debug builds).

Notes

• If your app calls OneSignal accessors (ex. OneSignal.User.oneSignalID) immediately after initWithContext, we recommend moving all OneSignal accessor calls off the main thread.
• No breaking API changes; existing initWithContext(context) continues to work as before.

We appreciate your experience and feedback using this alpha version!

5.1.37

Channels: Current

🐛 Bug Fixes

• fix(subs): Fix when multiple create subscription operations exist without token (#2354)
• fix (crash): Finishing the activity on main thread when a notification is opened (#2353)