Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
1 task done
ashleydee1999 opened this issue Sep 26, 2023 · 2 comments
Closed
1 task done

Comments

@ashleydee1999
Copy link

ashleydee1999 commented Sep 26, 2023

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

  • I agree to follow this project's Code of Conduct
@emawby
Copy link
Contributor

emawby commented May 20, 2024

@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
Copy link
Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants