[Bug]: optedIn is not being updated accordingly on Android

[luanalbineli]

What happened?

We have a screen where the user can opt in/out to push notifications. To get the current opt value, we use the following code (assuming that notification permissions are granted):

OneSignal.User.pushSubscription.optedIn

To opt in/out, we are using the following code (depending on user's choice):

// Opt out.
await OneSignal.User.pushSubscription.optOut();

// Opt in.
await OneSignal.User.pushSubscription.optIn();

After we close/open the app, or sometimes after a Hot Restart, the optedIn property no longer gets updated properly, after the opt in/out call.

On the background, the operation is enqueued and executed properly:

[main] OperationRepo.enqueue(operation: {"name":"update-subscription","appId":"APP_ID","onesignalId":
"ONE_SIGNAL_ID","subscriptionId":"SUB_ID","type":"PUSH","enabled":true,"address":"ADDRESS",
"status":"SUBSCRIBED"}, flush: false)

[DefaultDispatcher-worker-8] HttpClient: Request Sent = PATCH https://api.onesignal.com/apps/{APP_ID}/subscriptions/{SUB_ID}
Body: {"subscription":{"type":"AndroidPush","token":"TOKEN","enabled":true...}

On the example above, I've tried to opt in. I called await OneSignal.User.pushSubscription.optIn();, closed the screen, opened again, and the optedIn was still false.

I'm currently running the tests on a Physical Android device (Samsung S21 Ultra).

Steps to reproduce?

1. Install version 5.3.0.
2. Android user opens the app (with notification permissions granted).
3. User opt out from notifications.
4. User restarts the app.
4. User opt in.

What did you expect to happen?

OneSignal.User.pushSubscription.optedIn should be true. Instead is false.

OneSignal Flutter SDK version

5.3.0

Which platform(s) are affected?

• iOS
• Android

Relevant log output

Code of Conduct

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

[O-Nics]

same problem here in 5.3.3

the optIn() is done with success (push notifications accepted) but right after, and even with delay or retry, the optIN stays false or null

and by the way it works well on iOS

[nan-li]

Hi @luanalbineli and @O-Nicks apologies for the delay, I see {"name":"update-subscription","appId":"APP_ID","onesignalId": "ONE_SIGNAL_ID","subscriptionId":"SUB_ID","type":"PUSH","enabled":true,"address":"ADDRESS", "status":"SUBSCRIBED"} which indicates the subscription is enabled and this information is sent to the server.

Is the issue that the OneSignal.User.pushSubscription.optedIn boolean is false? Is the push subscription actually subscribed and the subscription in the dashboard are correct?

[luanalbineli]

Hi @luanalbineli and @O-Nicks apologies for the delay, I see {"name":"update-subscription","appId":"APP_ID","onesignalId": "ONE_SIGNAL_ID","subscriptionId":"SUB_ID","type":"PUSH","enabled":true,"address":"ADDRESS", "status":"SUBSCRIBED"} which indicates the subscription is enabled and this information is sent to the server.

Is the issue that the OneSignal.User.pushSubscription.optedIn boolean is false? Is the push subscription actually subscribed and the subscription in the dashboard are correct?

Hello @nan-li , sorry for the late answer as well. Unfortunately I'm no longer at the project that uses this code, but from the top of my mind the problem was that the OneSignal.User.pushSubscription.optedIn property was not synced properly on Android. The information was being pushed to the server, but the property (optedIn) was keeping the wrong value

[O-Nics]

Hi @luanalbineli and @O-Nicks apologies for the delay, I see {"name":"update-subscription","appId":"APP_ID","onesignalId": "ONE_SIGNAL_ID","subscriptionId":"SUB_ID","type":"PUSH","enabled":true,"address":"ADDRESS", "status":"SUBSCRIBED"} which indicates the subscription is enabled and this information is sent to the server.

Is the issue that the OneSignal.User.pushSubscription.optedIn boolean is false? Is the push subscription actually subscribed and the subscription in the dashboard are correct?

Hey @nan-li , same as @luanalbineli, I’m no longer on the project and same as him it was a sync problem, the .optin returned false instead of false, even if in OneSignal dashboard it was true

[dariowskii]

Any update on this issue?
We are having the same issue on the latest version