`Person 1` profile keeps coming back after being deleted - Cannot delete the 'Default' user profile

Test plan

See https://github.com/brave/brave-core/pull/13929

Description

• Recently a new profile named ‘Person 1’ started appearing in the menu. I cannot delete this account, and it is the default option when switching profiles, so it’s quite annoying.

Steps to Reproduce

Approach 1:

1. See undesired profile in menu named Person 1.
2. Go to “Manage People”, click on 3-dots button for Person 1, click ‘Delete this person’
3. Exit and restart brave.
4. Person 1 is back

Approach 2:

1. See undesired profile in menu named Person 1.
2. Open brave://version, look for Profile Path, which is ~/.config/BraveSoftware/Brave-Browser/Default
3. Delete that directory.
4. Restart Brave.
5. Person 1 is back. The directory is back.

Actual result:

Expected result:

Person 1 does not come back.

Reproduces how often:

Easily reproduced.

Brave version (brave://version info)

Brave | 0.62.51 Chromium: 73.0.3683.103 (Official Build)unknown (64-bit) Revision | e82a658d8159cabbd4938c1660f9bb00b4a82a23-refs/branch-heads/3683@{#902} OS | Linux

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields?

No.

• Does the issue resolve itself when disabling Brave Rewards?

Doubtful.

• Is the issue reproducible on the latest version of Chrome?

No. There is no unwanted profile when I open Chrome version 74.0.3729.131 (Official Build) (64-bit)

[gl-santos]

This error is still happening in Version 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)

There is a workaround:

1. Go to your .config folder (something like /home/youruser/.config/BraveSoftware/Brave-Browser);
2. Backup your Default, Profile 1, Profile 2, Profile 3… folders somewhere else (if anything goes wrong you can restore to your original state);
3. Close all Brave windows, delete the contents of Default folder and move the contents of any other profile to the Default folder. Then you can delete empty folder;
4. Restart Brave.

[Adeynack]

@FBorowiec @matthiasseghers

That workaround has fixed (or patched) it for me.