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

Each Android app opening generates a new session in "account/security/session-history" in the web app #281

Open
wizard86pz opened this issue Feb 11, 2025 · 6 comments
Labels

Comments

@wizard86pz
Copy link

wizard86pz commented Feb 11, 2025

Environment:

  • MEGA app Version(s): 15.0(250231359)(5b802e5)
  • OS Version(s): Android 15 | Build number: AP4A.250205.002
  • Devices/Simulators: Google Pixel 8a

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.

  1. Open the Android app, while you have already access to the account
  2. Check the session history list
  3. you'll see that a new and ongoing session is added, among all the Android ones. All of them are active and ongoing.

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.

@wizard86pz wizard86pz added the bug label Feb 11, 2025
@robinshi-mega
Copy link
Contributor

Thank you @wizard86pz for reporting this. We will investigate this issue and consider the improvement in upcoming releases.

@robinshi-mega
Copy link
Contributor

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:

  1. Go to "Settings > Help > Report issue"
  2. Input the problem descriptions
  3. Make sure you enable the "Send log file" toggle
  4. Click the send button on top right corner.
  5. Send me your MEGA user account ID so we can locate your report with logs. You may send here in GitHub comment, or email to [email protected] if you prefer.
    Thanks again.

@wizard86pz
Copy link
Author

wizard86pz commented Feb 11, 2025

Hello, is my "account ID" the email tied to the involved account?

@robinshi-mega
Copy link
Contributor

Yes, that's the email ID when you log in to MEGA app and website. Thanks @wizard86pz .

@wizard86pz
Copy link
Author

wizard86pz commented Feb 12, 2025

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.

Image

@wizard86pz
Copy link
Author

Hello, the issue is still occurring on the latest stable release v15.1 (250411204)

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

No branches or pull requests

2 participants