search

OneSignal / OneSignal-iOS-SDK

OneSignal is a free push notification service for mobile apps. This plugin makes it easy to integrate your native iOS app with OneSignal. https://onesignal.com
Other
496 stars 263 forks source link

[Bug]: Dashboard reports incorrect device info for devices sharing account #1323

Closed ashleydee1999 closed 4 months ago

ashleydee1999 commented 1 year ago

What happened?

Scenario: Say you do a fresh login on Phone A then you also log into Phone B afterwards using the same account. Then you use Phone A, OneSignal Dashboard will read that you were using Phone B, because the last device you did a fresh log into is the one whose records are updated.

For reporting and testing purposes, this makes things difficult, because it is not a true reflection of what's happening with my audience.

Steps to reproduce?

1. Get 2 devices and do fresh installs of an app with the OneSignal SDK
2. Do a OneSignal login on device A then close App. 
3. Do a OneSignal login on device B then close App.
4. Relaunch app on Device A
5. Visit the OneSignal Audience to see your subscriptions and you'll notice that the "Last Active" column that is updated is the one that belongs device B.

What did you expect to happen?

I expect the correct device records to be updated on the Audience (subscriptions).

OneSignal iOS SDK version

Release 5.0.1

iOS version

15

Specific iOS version

iOS 16

Relevant log output

No response

Code of Conduct

emawby commented 6 months ago

@ashleydee1999 I believe that the last active field is not updated until ending a session. This means that in the scenario you described the last active wouldn't update on device A until you close the app after launching from step 4. Is it not matching this behavior?

ashleydee1999 commented 4 months ago

@ashleydee1999 I believe that the last active field is not updated until ending a session. This means that in the scenario you described the last active wouldn't update on device A until you close the app after launching from step 4. Is it not matching this behavior?

Hi @emawby, this issue has been resolved after speaking to Jon. We setup a meeting and he managed to bring the issue to your dev team for fixing. Let me close the issue.