chore: Release 5.2.20

[onesignal-deploy]

Channels: Current

🛠️ Native Dependency Updates

• Update Android SDK from 5.1.38 to 5.4.0
  • 5.2.x - Identity Verification (JWT) - Feature is still in beta
  • 5.3.x - Custom Outcomes - Feature is still in beta
  • 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.
  • Feat: Detect for timezone changes and update the user (#2378)
  • add: security hardening around webview javaScriptEnabled (#2377)
  • Fix: ANR on POST to Outcomes endpoint (#2371)
  • ANR GmsLocationController timing out ([#2396][Bug]: GmsLocationController timing out OneSignal-Android-SDK#2396)
  • ANR [Bug]: ANR triggered by slow operations in main thread OneSignal-Android-SDK#2335
  • ANR [Bug]: ANR : initOneSignal OneSignal-Android-SDK#2266
  • ANR [Bug]: initWithContext OneSignal-Android-SDK#2397
  • ANR [Bug]: Request Permission OneSignal-Android-SDK#2399
  • ANR [Bug]: SharedPreferencesRead ANR OneSignal-Android-SDK#2400
  • Crash/ANR [Bug]: Crashes when OneSignal is used immediately after initiWithContext called OneSignal-Android-SDK#2192

  ---

  • 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.

---

This change is