[question]: After using OneSignal.login, why Users status changed to "Never Subscribed" on the dashboard?

[ayushi-sk]

How can we help?

After using OneSignal.login, why Users status changed to "Never Subscribed" on the dashboard?

Looks like the problem is kind of same https://github.com/OneSignal/OneSignal-Android-SDK/issues/2106

Same external ids might be causing the issue. But even after "allow permission", I am getting "Never subscribed"

Code of Conduct

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

[mtebele]

Same problem here. Any updates?

[TamilCodeRays]

I’m also facing the same issue, but I’m unable to reproduce it. I’ve lost nearly half a million users because of this.

[JneelaWhisker]

I'm also experiencing this issue in production using onesignal_flutter: ^5.3.4. Everything works perfectly fine on most devices, but we’re seeing this problem mainly on some Android devices. What’s unusual is that on the same device and with the same build, it sometimes works and then suddenly stops working. When it stops working:

• No new records appear in the OneSignal dashboard.
• Subscriptions become orphaned when they lack an external ID.
• iOS works perfectly fine; this issue seems isolated to Android.

It's hard to reproduce consistently, but it's definitely happening in real user scenarios. Hoping for a long-term fix or workaround soon.

[tddevel]

I am also experiencing this issue. SDK version: 5.1.37.

Most of my users have "Never Subscribed" status on the "Audience" page, while individual subscription pages display Status details: Permission Not Granted. Interestingly, some users obtain "Subscribed" status, and I see no pattern — they all have different Android versions, devices, etc. It seems similar to #2106 indeed.

I can reproduce the issue both in production and in a test app. It's enough to run it like this:

// build.gradle:
implementation("com.onesignal:OneSignal:5.1.37")

// MainActivity.kt, onCreate():
OneSignal.Debug.logLevel = com.onesignal.debug.LogLevel.VERBOSE
initWithContext(getApplicationContext(), "83...52")
CoroutineScope(Dispatchers.IO).launch {
    OneSignal.Notifications.requestPermission(true)
}
login("test-1234")

[jinliu9508]

@tddevel @JneelaWhisker For subscriptions that appear to have the wrong subscribed status, could you check whether the push token is missing? Certain Android devices have FCM disabled or not functioning properly, which prevents OneSignal from registering and maintaining a valid push subscription.

[tddevel]

check whether the push token is missing

@jinliu9508 In my case, the push token is not missing. I also see many users experiencing this problem. I don't think they all have no FCM tokens.

I managed to sniff traffic between the application with OneSignal SDK and OneSignal backend — it sends a valid FCM token.

Removing .login() call or changing SDK version fixes the problem. I opened new issue #2418 to describe all findings.