meganz
Each Android app opening generates a new session in "account/security/session-history" in the web app
Environment:
- MEGA app Version(s): 15.0(250231359)(5b802e5988)
- 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.
- Open the Android app, while you have already access to the account
- Check the session history list
- 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.
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:
- Go to "Settings > Help > Report issue"
- Input the problem descriptions
- Make sure you enable the "Send log file" toggle
- Click the send button on top right corner.
- 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.
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, I'm waiting to reach the v15.4 (https://github.com/meganz/android/releases/tag/v15.4). It has been released since 4 days, but still not visibile in the Google Play Store. Can you confirm the update has been reviewed and approved by Google, to release it publicly via Play Store?
CC @robinshi-mega
Hi @wizard86pz , v15.4 has been approved by Google, but it is in phased release, and it's not rolled out to 100% users yet. We expect to fully release it in next couple of days. 👍
Hi @wizard86pz , v15.4 has been approved by Google, but it is in phased release, and it's not rolled out to 100% users yet. We expect to fully release it in next couple of days. 👍
Hello, yes I did know well. But I didn't imagine that the rolling phase was longer than 4 days, thanks.
Hello, bad news @robinshi-mega. I've tested again on v15.4.1, with a fresh access. I've not opened any cookies setting, and after some minutes I've see the client's session duplicated.
I've sent a report with logs with the present comment link.
Ticket ID: KMJ-609-52242
Hi @wizard86pz , our team have found the ticket ID, but log file isn't found in there. Could you please try and send again? Many thanks.
Hello @robinshi-mega, I've just reached v15.5 and its testing regarding the thread's topic. I'll let you know in case I still face the issue, and new log sending.
Hello @robinshi-mega, I'm sorry to notify you that I still see the issue in the v15.8. I noted this even when I logged in from a fresh installation on my device and then waited just 5 minutes. The session is augmented by 1 or 3 sometimes: I mean, I see 3 sessions tied to a single login access action. It's becoming quite frustrating to have this misleading view on a very sensitive point, such as access to my cloud space.
I've chosen MEGA service since I think that your (the whole Company's) deserves trust and it's quite eligible for a payment effort on my side to have a great service...but I have to frankly share that it's quite disappointing.
I tried my best to give you all the info, logs, and so on. But if it's not fixed, I'd consider stopping using the service (and not just from the Android app) for a period until it's fixed.
It's not an ultimatum, it's frank and clear advice to take into consideration this issue, which probably needs more effort than what done so far...since I underline, it's occurring in an extremely crucial and sensible point: instances access management.
Many thanks again @wizard86pz, and sorry for the frustrations. Last time our helpdesk team didn't manage to receive the logs you sent us. But it's great that this time you have the steps to reproduce. We will try to reproduce in our side and investigate it with priority.
Hello @robinshi-mega, I can confirm that the issue seems to have been completely fixed in Android app v5.12, finally. Thanks a lot for your and your team's work.