New issue
Advanced search Search tips

Issue 784403 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 17
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Application chrome error if it stores too many account and password data.

Reported by reyaga...@gmail.com, Nov 13 2017

Issue description

Either this is a problem in the Chrome 62.0. 3202.84 app or the errors of the android OS 6.0.1 system, I do not know the obvious. So I report to you this problem.

I saved my first Facebook account with phone number 085733837050 with a deathnote password (password sample only). Then I also enter a second account with reynandabqari25@gmail.com email and also use the same password as the first account (085733837050). When my first account was removed and removed from the chrome app, then I signed in with the second account (reynandabqari25@gmail.com), which should be the second account read not first. Maybe this is a problem with the system. Please reply to my report, 
 

Comment 1 by reyaga...@gmail.com, Nov 13 2017

Bug chrome.mp4
22.9 MB Download

Comment 2 by reyaga...@gmail.com, Nov 14 2017

The reynandabqari25@gmail.com account should have been signed in not the first account 085733837050 that has been deleted

Comment 3 by zea@chromium.org, Jan 17 2018

Components: -Services>Sync UI>Browser>Passwords
Seems more like a password issue, not a sync issue.

Comment 4 by reyaga...@gmail.com, Jan 18 2018

Lalu apa langkah selanjutnya? 

Comment 5 by battre@chromium.org, Jan 19 2018

Can you try to describe your problem in other words? Unfortunately, I don't understand what happens and what is expected.

Comment 6 by reyaga...@gmail.com, Jan 19 2018

Masalahnya adalah sistem aplikasi chrome seperti tidak mampu membedakan antara akun A dan B, memang 2 akun menggunakan sandi yang sama dan seharusnya sistem aplikasi HARUS bisa membedakan antara akun A dan B meski sandinya sama.

Saya harap perbaikan di sistem aplikasi, karena sekarang banyak orang yang membeli perangkat bekas, saya kawatir jika kebetulan sandi yang digunakan sama, maka orang lain bisa masuk akun pemilik perangkat lama.
Status: Untriaged (was: New)
Issue moved from a project with a different set of status labels. "New" is not a supported status in /p/chromium, so these ended up in a black-hole.
 Issue 922052  has been merged into this issue.

Comment 9 by kolos@chromium.org, Jan 17 (6 days ago)

Status: Archived (was: Untriaged)
Chrome cannot mix accounts with different usernames (085733837050 and reynandabqari25@gmail.com). 

If you want to continue the discussion. Please re-open the bug and describe the problem with the following pattern in English:
What steps will reproduce the problem?
(1)
(2)
(3)

What is the expected result?


What happens instead?


Comment 10 by reyaga...@gmail.com, Jan 17 (6 days ago)

problem A
1. I saved my first Facebook account with phone number 085733837050 with a death note password (only password samples).
2. Then I also enter the second account with the email reynandabqari25@gmail.com and also use the same password as the first account (085733837050).

when my first account was deleted and deleted from the chrome application, then I entered with a second account (reynandabqari25@gmail.com), which should be the second account that was read not the first. this problem on facebook.com

problem B
1. I save account A in chrome with the name Reyagam74@gmail.com then enter.
2. automatically all data in account A is seen in chrome.
3. I enter account B again with the name reynandabqary25@gmail.com but with a different password when entering chrome.
3. then I register and login to the hackerone.com site using account A and B that use a different name but use the same password on hackerone.com
4. when I delete account B from chrome (after logging out and deleting data in application settings from the device).
5. I log in again in chrome and hackerone using account A, but the results remain in with account B that I deleted.

data that has been removed from chrome should have been updated and not affected.

Sign in to add a comment