Skip to content

Conversation

@onesignal-deploy
Copy link
Collaborator

@onesignal-deploy onesignal-deploy commented Jan 8, 2026

Channels: Current

🛠️ Native Dependency Updates

  • Update Android SDK from 5.1.37 to 5.4.2
    • feat: Enable docs (#2507)
    • 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)
    • chore: Kotlin 1.9 update (#2403)
    • chore: Bump firebase-messaging to 24.0.0 (#2149)

    • feat: Enable docs (#2507)
    • feature: Exposing accessors thru suspend (#2502)
    • bug: catch exception if opening a notification fails (#2508)
    • fix: a rare NPE from PermissionViewModel introduced in 5.4.0 (#2504)
    • fix: IAM with NOT_EQUAL_TO trigger always shows up (#2509)
    • fix: NPE in SyncJobService since 5.4 (#2500)
    • fix: NPE when setting timezone on app focus (#2505)
    • 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)
    • Improvement: failure message shows that appID is missing (#2506)
    • improvement: Offloaded work on background threads. (#2394)
    • chore: Kotlin 1.9 update (#2403)
    • chore: Bump firebase-messaging to 24.0.0 (#2149)


    • Feat: Detect for timezone changes and update the user (#2378)
    • Fix: ANR on POST to Outcomes endpoint (#2371)
    • add: security hardening around webview javaScriptEnabled (#2377)

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

    • 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).
    • 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.
    • JWT: Resolve IAM conditions after user create to allow fetching of IAMs in JWT: Resolve IAM conditions after user create to allow fetching of IAMs OneSignal-Android-SDK#2337
    • rebased with 5.1.35 which include the following:
    • #2327
    • #2329
    • #2328
    • #2330
    • #2332
    • #2333
    • This limitation will be addressed in the next version
    • Switched publishing to use the Central Publisher Portal
    • No changes to those using the SDK in their project
    • Rebased to 5.1.34 for more bug fixes and stability improvements.
    • Adds the following new public methods #2311:
    • OneSignal.Debug.addLogListener
    • OneSignal.Debug.removeLogListener
    • Rebased to 5.1.33 for more bug fixes and stability improvement.
    • Feat: Detect for timezone changes and update the user (#2378)
    • Fix: ANR on POST to Outcomes endpoint (#2371)
    • add: security hardening around webview javaScriptEnabled (#2377)


This change is Reviewable

@fadi-george
Copy link
Collaborator

Needs to check release build/version for android example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants