-
Notifications
You must be signed in to change notification settings - Fork 373
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
Each Android app opening generates a new session in "account/security/session-history" in the web app #281
Comments
Thank you @wizard86pz for reporting this. We will investigate this issue and consider the improvement in upcoming releases. |
Hi @wizard86pz , as we are investigating this issue, may we request you to send us the trace logs? It will greatly help us get more idea of what's happening in your device. Thank you very much! Steps:
|
Hello, is my "account ID" the email tied to the involved account? |
Yes, that's the email ID when you log in to MEGA app and website. Thanks @wizard86pz . |
I've sent the logs from the Android app of Mega and an email to [email protected] from the impacted account ID email. P.s.: this is what I mean: multiple session, cloned from a single ap/device usage of my Mega account. |
Hello, the issue is still occurring on the latest stable release v15.1 (250411204) |
Environment:
Describe the bug
All the time I open the Android app, it creates a new session in the list of ongoing sessions. I do not put any credentials in the app, and it maintains the access validity, but at every opening, I see that a new session is added to the web app session history list.
Reproduction Steps
Add the different steps to reproduce the behavior.
Expected behavior
As it has already correctly happened in the past, before the last update, the server should not manage the opening of the app by creating a new session in the list.
Additional context
It seems that on the server side, the session of the same device and app is not recognized as an already existing instance.
The text was updated successfully, but these errors were encountered: