.google.com cookie mismatch after import

[darkdh]

Test plan

#11647 (comment)

---

Description

Import cookies from Chrome/Firefox will cause cookie mismatch error on google.com

Steps to Reproduce

1. Clean cookies on Chrome/Firefox and login in google account
2. Import cookies from Chrome/Firefox to Brave
3. Login google account on Brave

Actual result:

Expected result:
No cookie mismatch error
Reproduces how often: [What percentage of the time does it reproduce?]
100%

Brave Version

0.19.36
about:brave info:

Brave: 0.19.36
rev: d24779f
Muon: 4.4.25
libchromiumcontent: 61.0.3163.100
V8: 6.1.534.41
Node.js: 7.9.0
Update Channel: Beta
OS Platform: macOS
OS Release: 16.7.0
OS Architecture: x64
Reproducible on current live release:

Yes

Additional Information

Opera has the same problem
related to #11356

[darkdh]

cc @bbondy

[kjozwiak]

Using the STR from #11401 (comment), went through the following verification:

• macOS 10.12.6 x64 - (imported cookies from Chrome/Chromium/Firefox) - PASSED
• Win 10 x64 - (imported cookies from Chrome/Chromium/Firefox) - PASSED

[darkdh]

chrome doesn't actually work

[tomasdev]

Having this issue not by importing. Simply sign into 2 or 3 different gmail accounts and it breaks. Perhaps the Block 3rd party should have a configurable list of domain exceptions.

[jonathansampson]

@tomasdev We're able to set exceptions, but aim to do so with caution. I am regularly signed into 2 GMail accounts (without any issue). Would you be available to hop on a Skype or Google Hangout call sometime? I'd love to see the problem first-hand.

[Hjohnson14]

Hi all,
I'm having this problem too. I've tried both clearing cookies on Chrome and then importing the data to Brave and allowing all cookies for Google on the site shield setting, but neither has worked. Is there another solution? Access to gmail is essential to my browser usage.

[tomasdev]

@Hjohnson14 what I did to fix it was Preferences » Shields » Cookie Control: Allow all cookies until there's an option to whitelist 3rd party cookies per domain

@jonathansampson absolutely! you can see my email in my GH profile (signed in)

[jonathansampson]

Thank you, @tomasdev. I'll email you shortly :)

[LaurenWags]

Verified on macOS 10.12.6 x64 using the following build:

• 0.22.7 8bb7e77
• libchromiumcontent: 65.0.3325.181
• muon: 5.1.1

Verified on Windows 7 x64

• 0.22.7 8bb7e77
• libchromiumcontent: 65.0.3325.181
• muon: 5.1.1

Verified on Mint 18.3 x64 using the following build:

• 0.22.11 56de947
• libchromiumcontent: 65.0.3325.181
• muon: 5.1.2

[mikeongit]

What worked for me was to navigate to google.com and deactivate the Brave Shield.
Deactivating it for accounts.google.com only didn't do the trick for me, you also have to explicitly deactivate for the google.com domain.

Next, I signed in and was able to access my mail without any trouble.

[walker2]

@mikeongit
Thanks, your solution worked.

[kjozwiak]

@mikeongit @walker2 were guys importing cookies from either Firefox or Chrome? Or did you run into this issue when migrating from the muon version of Brave (old)?

[mikeongit]

Heya, I imported cookies from both, Firefox and Chrome.

[walker2]

@kjozwiak Yeah just imported everything from Firefox

[kjozwiak]

@mikeongit @walker2 the Brave muon version isn't being supported anymore. I would suggest switching to the new version of the browser which can be found here:

• https://brave.com/download (Download Link)
• https://github.com/brave/brave-browser/ (GitHub Page)

We also have a dev and beta channel which can be found here:

• https://brave.com/download-dev
• https://brave.com/download-beta