[fadi-george]

Description

One Line Summary

Fix setLanguage('') on Android so it resets to the device language, and standardize the demo push UI.

Details

Motivation

The Android bridge turned '' into null, but native setLanguage(value: String) rejects null, so setLanguage('') likely crashed with a NullPointerException instead of resetting to the device language as the Dart docs say. iOS already passed '' through. The demos need this for their Device Default language option. Part of SDK-5300 (standardize push subscription UI across SDK demo apps). Matches the Android demo (OneSignal/OneSignal-Android-SDK#2760).

Scope

SDK fix: OneSignalUser.java passes '' through to native. Native Android has resolved '' to the device language since 5.10.1; this plugin ships 5.10.2. No other bridge behavior changes.

Demo (examples/demo and examples/demo-pods):

• Push section: new read-only Status row above the toggle. It shows Subscribed only when the user is opted in, notification permission is granted, and a push token is present; otherwise Unsubscribed. It updates from the existing subscription and permission observers, and the push token is now tracked too.
• The toggle label changes from "Enabled" to Opted In. The existing test ID is unchanged, so Appium selectors still work. The status row uses push_subscription_status, same as Android.
• User section: new Language row after External ID with Device Default plus the same 43 languages, in the same order, as Android and iOS (user_language_dropdown). It calls setLanguage(code), and Device Default sends '', which the native SDK resolves to the device language. The choice is saved only so the picker shows it after a restart; it is not re-sent at launch, since native keeps its own value. Logout resets it to Device Default, as Android and iOS do.

Testing

Unit testing

Root flutter test: 272 passed, coverage 98.2%. No new Dart test: the Dart side was already correct and the bug was in the Java bridge, which has no unit test harness.

Manual testing

flutter analyze (root clean; demos only show 2 warnings that were already there), Java spotless check passes, and the examples/demo debug APK builds. Not yet run on a device or simulator.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

🤖 Generated with Claude Code

[abdulraqeeb33]

Bridge fix checks out: native core 5.10.1+ resolves '' to the device language and the plugin pins 5.10.2. Demo changes match the other SDKs.