# Cookie Settings Bug

**URL:** <https://community.brave.app/t/cookie-settings-bug/506418>\
**Category:** Mobile Support\
**Tags:** android\
**Created:** [September 18, 2023, 3:51pm UTC](https://community.brave.app/t/cookie-settings-bug/506418 "2023-09-18T15:51:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 18, 2023, 3:51pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/1 "2023-09-18T15:51:13Z")

</div>

There is a bug in the shield settings of Brave for Android, which causes changes to the cookie settings to be ineffective, automatically reverting them to ‘allow all cookies.’

[https://global.discourse-cdn.com/brave/original/3X/6/7/67b95fd228b55dddb4e1dba317779cacdc0105b9.mp4](https://global.discourse-cdn.com/brave/original/3X/6/7/67b95fd228b55dddb4e1dba317779cacdc0105b9.mp4)

A potential workaround involves navigating to site settings and selecting the option to block third-party cookies. However, a noteworthy issue persists: when users revisit the shield settings and simply click “done” without making any modifications, the setting reverts back to ‘allow all cookies’ without requiring any additional user input.

This problem has been a point of concern for numerous users on Brave’s subreddit for several months. Below are links to some of these discussions.  
• [https://reddit.com/r/brave\_browser/s/X055e8p4d6](https://reddit.com/r/brave_browser/s/X055e8p4d6)  
• [https://reddit.com/r/brave\_browser/s/FZvLm2aYg6](https://reddit.com/r/brave_browser/s/FZvLm2aYg6)  
• [https://reddit.com/r/brave\_browser/s/S6tKEWFY3Q](https://reddit.com/r/brave_browser/s/S6tKEWFY3Q)

---

<div class="post-metadata">

**Author:** ![Saoiray](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/saoiray/32/212354_2.png) [@Saoiray](https://community.brave.app/u/Saoiray)\
**Post date:** [September 18, 2023, 4:24pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/2 "2023-09-18T16:24:08Z")

</div>

@user07 it’s just a visual glitch. I just tested on my Android (and could upload a video if necessary). You’re right that if you go to `Allow all cookies` and then go to switch to `Block cross-site cookies` that the menu appears to switch back automatically to `Allow all cookies`. But when I hit back on the menu and then clicked on `Brave Shields & Privacy` again, it loaded with my setting at `Block cross-site cookies` just as I had selected.

Would you check this yourself?

---

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 18, 2023, 5:42pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/3 "2023-09-18T17:42:19Z")

</div>

> [@Saoiray](#):
>
> Would you check this yourself?

@Saoiray That too is a visual glitch; it just shows that cross-site cookies are blocked after exiting and reopening, but in reality, they aren’t. You can verify it by visiting any website and then tapping the Brave Shield icon or by going to Settings → Site Settings → Cookies; you’d find that all cookies are allowed. I’ve already tested it thoroughly before posting here.

Also, in the first attached reddit link, a user has already mentioned doing it, and you can find the OP’s response [here](https://www.reddit.com/r/brave_browser/comments/16431nm/theres_a_serious_android_bug_cant_use_brave_due/jy6wy5m/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button).

---

<div class="post-metadata">

**Author:** ![Saoiray](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/saoiray/32/212354_2.png) [@Saoiray](https://community.brave.app/u/Saoiray)\
**Post date:** [September 18, 2023, 5:51pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/5 "2023-09-18T17:51:23Z")

</div>

@user07 okay, so just tested and it does seem like they don’t adjust each other necessarily. But if you change both to third party only, then it remains that setting. I’m going to look to see if there’s an open Github on this by chance. If not, I’ll make one.

 ![Screenshot_20230918-134924_Brave](https://global.discourse-cdn.com/brave/original/3X/2/e/2efae471d529ca92d216d70c00eaf885c3d7419a.jpeg)

 ![Screenshot_20230918-134902_Brave](https://global.discourse-cdn.com/brave/original/3X/c/e/ce5383625802f93c0d7e078c221b2425f86c7654.jpeg)

---

<div class="post-metadata">

**Author:** ![Saoiray](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/saoiray/32/212354_2.png) [@Saoiray](https://community.brave.app/u/Saoiray)\
**Post date:** [September 18, 2023, 5:54pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/6 "2023-09-18T17:54:59Z")

</div>

It looks like there’s an open Github on this over as shown below:

> <https://github.com/brave/brave-browser/issues/30155>
>
> \<!-- Have you searched for similar issues? Before submitting this issue, please …check the open issues and add a note before logging a new issue. 
> 
> PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
> INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--\>
> 
> \## Description 
> 
> The "Block cross-site Cookies" option is not saved in Brave Shields advanced settings
> 
> \## Steps to reproduce 
> 
> 1. Launch Brave \> Hamburger Menu \> Settings
> 2. Brave Shields & privacy \> Block Cookies
> 3. Set to \`Block all cookies\` or \`Allow all cookies\` \> Done
> 4. Open Block Cookies again \> Set to \`Block cross-site cookies\` \> Done \> Observe
> 
> \## Actual result 
> 
> The \`Block cross-site cookies\` option is not saved in Brave Shields advanced settings while staying on that page. It's always switching to \`Allow all cookies\` instead. If you want to save cookies in the \`Block cross-site cookies\` state, then need to close the \`Brave Shields & privacy\` settings or Brave itself.
> 
> https://user-images.githubusercontent.com/128532965/236368773-4aba8454-2d63-44be-aa38-53d9801d8b26.mp4
> 
> \## Expected result
> 
> The \`Block cross-site cookies\` state must be saved without leaving \`Brave Shields & privacy\` settings or closing Brave
> 
> \## Issue reproduces how often 
> 
> Easily reproduced
> 
> \## Version/Channel Information:
> 
> 
> \- Can you reproduce this issue with the current Play Store version? Yes
> \- Can you reproduce this issue with the current Play Store Beta version? Yes
> \- Can you reproduce this issue with the current Play Store Nightly version? Yes
> 
> \## Device details
> - Install type (ARM, x86): ARM
> - Device type (Phone, Tablet, Phablet): Pixel 6 \[phone\]
> - Android version: Android 13 \[oriole-user 13 TQ2A.230405.003.E1 release-keys\]
>    
> \## Brave version
> 
> 1.52.86 Chromium: 113.0.5672.77 (Official Build) beta (32-bit)
> 
> \### Website problems only
> \- Does the issue resolve itself when disabling Brave Shields? 
> \- Does the issue resolve itself when disabling Brave Rewards?
> \- Is the issue reproducible on the latest version of Chrome? 
> 
> \### Additional information

I’m going to tag @Mattches on this as well for awareness. I’ll go ahead and add a +1 and some information over on that as well.

---

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 18, 2023, 6:18pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/7 "2023-09-18T18:18:26Z")

</div>

> [@Saoiray](#):
>
> But if you change both to third party only, then it remains that setting.

Yes, but you don’t need to change both; it can be done by going into Settings → Site Settings → Cookies and selecting ‘Block Third-Party Cookies’.

However, one thing to keep in mind and is another major bug too, which occurs without any user input:

> [@user07](#):
>
> However, a noteworthy issue persists: when users revisit the shield settings and simply click “done” without making any modifications, the setting reverts back to ‘allow all cookies’ without requiring any additional user input.

You can check on yours @Saoiray

---

<div class="post-metadata">

**Author:** ![Saoiray](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/saoiray/32/212354_2.png) [@Saoiray](https://community.brave.app/u/Saoiray)\
**Post date:** [September 18, 2023, 6:24pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/8 "2023-09-18T18:24:40Z")

</div>

> [@user07](#):
>
> You can check on yours @Saoiray

Yeah, I checked that. It still is the behavior I mentioned earlier. It will show as if it switched to `Allow all cookies` but if you click back and then enter the menu again, it will show `Block cross-site cookies`. At least is how it worked when I tried it.

Yes, if I click on it and it opens the choices, then I tap anywhere else or choose an option, it will show `Allow all cookies`. But again, if I click `<` and enter `Brave Shields & privacy` again, it will show `Block cross-site cookies` as my selection (assuming I had last tapped on that)

---

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 18, 2023, 6:52pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/9 "2023-09-18T18:52:10Z")

</div>

> [@Saoiray](#):
>
> But again, if I click `<` and enter `Brave Shields & privacy` again, it will show `Block cross-site cookies` as my selection (assuming I had last tapped on that)

But that would be just a false positive, which can be verified by going into site settings.

What I actually meant to say is that when a user installs Brave on Android and doesn’t change any cookie settings in the Shields settings, they simply tap to view the default cookie settings applied, and then tap back or done. Here, it reverts to ‘Allow all cookies’ by itself without any user input. Even if someone like us, who knows about the bug and the workaround for cookies that can only be done via site settings, goes into the Shield settings, taps on cookies, doesn’t input anything, and taps the ‘Done’ button, understanding what has been applied will still be that way. Boom! Once again, it has changed to ‘Allow all cookies’ without any user input.

---

<div class="post-metadata">

**Author:** ![Saoiray](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/saoiray/32/212354_2.png) [@Saoiray](https://community.brave.app/u/Saoiray)\
**Post date:** [September 18, 2023, 7:10pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/10 "2023-09-18T19:10:43Z")

</div>

@user07 I guess let me show you what I am seeing on testing.

[![](https://global.discourse-cdn.com/brave/original/3X/c/8/c82fd40dbbb191de3f3f22fee1de5e1af26a6c0b.jpeg "Android cookies test") ](https://www.youtube.com/watch?v=0QpdKJqQz_0)

---

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 18, 2023, 7:46pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/11 "2023-09-18T19:46:28Z")

</div>

You’re exactly seeing what is actually the bug and is same here. I don’t understand why it became confusing even though I’ve kept everything clear since the beginning. As I’ve seen in our conversation and in your video too, you emphasized closing and reopening shield settings more, but that isn’t the concern, and it doesn’t fix anything. I’ve already addressed this here:

> [@user07](#):
>
> @Saoiray That too is a visual glitch; it just shows that cross-site cookies are blocked after exiting and reopening, but in reality, they aren’t. You can verify it by visiting any website and then tapping the Brave Shield icon or by going to Settings → Site Settings → Cookies; you’d find that all cookies are allowed. I’ve already tested it thoroughly before posting here.
> 
> Also, in the first attached reddit link, a user has already mentioned doing it, and you can find the OP’s response [here](https://www.reddit.com/r/brave_browser/comments/16431nm/theres_a_serious_android_bug_cant_use_brave_due/jy6wy5m/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button).

The real matter is that if anyone has even touched the cookies in shield settings and didn’t choose any options, the browser-level cookie settings revert to allowing all cookies.

---

<div class="post-metadata">

**Author:** ![callidae](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@callidae](https://community.brave.app/u/callidae)\
**Post date:** [September 19, 2023, 3:41pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/12 "2023-09-19T15:41:13Z")

</div>

> [@user07](#):
>
> There is a bug in the shield settings of Brave for Android, which causes changes to the cookie settings to be ineffective, automatically reverting them to ‘allow all cookies.’

Same issue here

> [@user07](#):
>
> A potential workaround involves navigating to site settings and selecting the option to block third-party cookies. However, a noteworthy issue persists: when users revisit the shield settings and simply click “done” without making any modifications, the setting reverts back to ‘allow all cookies’ without requiring any additional user input.

Didn’t know that there’s a workaround for it, thanks. I thought I must have messed up something during setup. 😅 And will keep in mind to not tap cookies in shield settings after applying workaround until this gets fixed. Saw those reddit posts too, this has been floating around for months and hasn’t been fixed yet. Anyways, I’ll wait until the brave team gets this fixed soon, and I hope it won’t take months for such a serious bug.

---

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 19, 2023, 6:05pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/13 "2023-09-19T18:05:52Z")

</div>

> [@callidae](#):
>
> Saw those reddit posts too, this has been floating around for months and hasn’t been fixed yet. Anyways, I’ll wait until the brave team gets this fixed soon, and I hope it won’t take months for such a serious bug.

I’m hopeful, but my optimism is waning as I’ve come across numerous reddit posts, comments, and gitHub issues that have persisted for months without any indication of a resolution in sight.

One of the comments from attached link:

 ![](https://global.discourse-cdn.com/brave/original/3X/a/b/abb2471cd59a4e5fb3b0e3221eb9508924705eca.jpeg)

---

<div class="post-metadata">

**Author:** ![callidae](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@callidae](https://community.brave.app/u/callidae)\
**Post date:** [September 19, 2023, 7:31pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/14 "2023-09-19T19:31:47Z")

</div>

Hey @Mattches, sorry for the tag; I just wanted to have your attention on this. This is a major bug that has been there for months, affecting almost all devices running brave on android.

---

<div class="post-metadata">

**Author:** ![Saoiray](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/saoiray/32/212354_2.png) [@Saoiray](https://community.brave.app/u/Saoiray)\
**Post date:** [September 19, 2023, 7:59pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/15 "2023-09-19T19:59:35Z")

</div>

@callidae I just want to make sure you noticed I shared an open Github issue for it. If you click and read through, you’ll see someone assigned it to themselves in July. This means it’s a project in motion.

> <https://github.com/brave/brave-browser/issues/30155>
>
> \<!-- Have you searched for similar issues? Before submitting this issue, please …check the open issues and add a note before logging a new issue. 
> 
> PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. 
> INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--\>
> 
> \## Description 
> 
> The "Block cross-site Cookies" option is not saved in Brave Shields advanced settings
> 
> \## Steps to reproduce 
> 
> 1. Launch Brave \> Hamburger Menu \> Settings
> 2. Brave Shields & privacy \> Block Cookies
> 3. Set to \`Block all cookies\` or \`Allow all cookies\` \> Done
> 4. Open Block Cookies again \> Set to \`Block cross-site cookies\` \> Done \> Observe
> 
> \## Actual result 
> 
> The \`Block cross-site cookies\` option is not saved in Brave Shields advanced settings while staying on that page. It's always switching to \`Allow all cookies\` instead. If you want to save cookies in the \`Block cross-site cookies\` state, then need to close the \`Brave Shields & privacy\` settings or Brave itself.
> 
> https://user-images.githubusercontent.com/128532965/236368773-4aba8454-2d63-44be-aa38-53d9801d8b26.mp4
> 
> \## Expected result
> 
> The \`Block cross-site cookies\` state must be saved without leaving \`Brave Shields & privacy\` settings or closing Brave
> 
> \## Issue reproduces how often 
> 
> Easily reproduced
> 
> \## Version/Channel Information:
> 
> 
> \- Can you reproduce this issue with the current Play Store version? Yes
> \- Can you reproduce this issue with the current Play Store Beta version? Yes
> \- Can you reproduce this issue with the current Play Store Nightly version? Yes
> 
> \## Device details
> - Install type (ARM, x86): ARM
> - Device type (Phone, Tablet, Phablet): Pixel 6 \[phone\]
> - Android version: Android 13 \[oriole-user 13 TQ2A.230405.003.E1 release-keys\]
>    
> \## Brave version
> 
> 1.52.86 Chromium: 113.0.5672.77 (Official Build) beta (32-bit)
> 
> \### Website problems only
> \- Does the issue resolve itself when disabling Brave Shields? 
> \- Does the issue resolve itself when disabling Brave Rewards?
> \- Is the issue reproducible on the latest version of Chrome? 
> 
> \### Additional information

---

<div class="post-metadata">

**Author:** ![callidae](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@callidae](https://community.brave.app/u/callidae)\
**Post date:** [September 20, 2023, 10:48am UTC](https://community.brave.app/t/cookie-settings-bug/506418/16 "2023-09-20T10:48:40Z")

</div>

> [@Saoiray](#):
>
> I just want to make sure you noticed I shared an open Github issue for it. If you click and read through, you’ll see someone assigned it to themselves in July. This means it’s a project in motion.

@Saoiray Yes, I’ve already seen that. I’ve tagged `@Mattches` here just to ensure he’s aware of it and can prioritize it if necessary.

---

<div class="post-metadata">

**Author:** ![Mattches](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/mattches/32/25189_2.png) [@Mattches](https://community.brave.app/u/Mattches)\
**Post date:** [September 20, 2023, 5:10pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/17 "2023-09-20T17:10:13Z")

</div>

I’ve pinged some team members internally as well as in the thread to hopefully get more eyes on this.

Thank you

---

<div class="post-metadata">

**Author:** ![DJT48](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/djt48/32/167280_2.png) [@DJT48](https://community.brave.app/u/DJT48)\
**Post date:** [September 20, 2023, 9:31pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/18 "2023-09-20T21:31:35Z")

</div>

Just to thank you, I’m not a developer but I appreciate the workaround.

---

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 21, 2023, 9:36am UTC](https://community.brave.app/t/cookie-settings-bug/506418/19 "2023-09-21T09:36:40Z")

</div>

> [@Mattches](#):
>
> I’ve pinged some team members internally as well as in the thread to hopefully get more eyes on this.

Thanks a lot! @Mattches

---

<div class="post-metadata">

**Author:** ![Mattches](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/mattches/32/25189_2.png) [@Mattches](https://community.brave.app/u/Mattches)\
**Post date:** [September 21, 2023, 4:22pm UTC](https://community.brave.app/t/cookie-settings-bug/506418/20 "2023-09-21T16:22:57Z")

</div>

Looks like we got some movement on the issue — priority and status of the issue has been updated 👍

---

<div class="post-metadata">

**Author:** ![user07](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@user07](https://community.brave.app/u/user07)\
**Post date:** [September 22, 2023, 11:19am UTC](https://community.brave.app/t/cookie-settings-bug/506418/21 "2023-09-22T11:19:04Z")

</div>

> [@Mattches](#):
>
> Looks like we got some movement on the issue — priority and status of the issue has been updated 👍

Yeah, hoping it’ll finally be fixed and won’t take any longer.

[Next page](https://community.brave.app/t/cookie-settings-bug/506418.md?page=2)