[Bug]: iOS: addTagWithKey does not apply

[ftl-huongdv]

What happened?

On iOS Release builds, the user logs in, calling addTagWithKey does not apply the tag — the SDK returns no error but the tag never appears on OneSignal. If the user try again, the tag is applied successfully. This only happens on iOS in Release mode

Steps to reproduce?

Install the app from App Store

Launch app

Initialize OneSignal:

OneSignal.initialize(APP_ID);
OneSignal.Notifications.requestPermission(true);


User logs in

Call:

await OneSignal.User.addTagWithKey('userId', userId);


Tag is not applied

Logout, OneSignal.User.removeTag('userId') → login again

Tag is applied successfully

What did you expect to happen?

OneSignal.User.addTagWithKey('userId', 'user.$userId') works fine

OneSignal Flutter SDK version

5.3.4

Which platform(s) are affected?

• iOS
• Android

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[ftl-huongdv]

I just upgraded from onesignal_flutter ^3.3.2 to ^5.3.4

[nan-li]

Hi @ftl-huongdv thanks for reporting. Do you have complete logs from the SDK? Turn on verbose logging with OneSignal.Debug.setLogLevel(OSLogLevel.verbose).

You can share your logs here, or share the logs with support@onesignal.com and reference this GitHub issue, and also mention my name.

[cuongpitpaylak]

Hi @ftl-huongdv thanks for reporting. Do you have complete logs from the SDK? Turn on verbose logging with OneSignal.Debug.setLogLevel(OSLogLevel.verbose).

You can share your logs here, or share the logs with support@onesignal.com and reference this GitHub issue, and also mention my name.

Hello @nan-li , thank for your support
I cannot reproduce this bug when debugging; it only happens with my customers.

[nan-li]

@cuongpitpaylak without logs it would be hard to say what is happening. Perhaps you could be encountering a tags over limit error for the user?

[fadi-george]

Hi @ftl-huongdv, thanks for taking the time to report this.
We haven't heard back with additional details in a while, so we're going to close this one out for now. If you're still experiencing this issue, please feel free to reopen with any relevant logs or a minimal reproduction.