Unable to login to YouTube on Android using Brave browser

**Description of the issue: I have been unable to login to my YouTube account using Brave browser on my android phone. Works well on desktop though. Everytime, I login (provide google username and password), it redirects here - https://m.youtube.com/channel/UChf_Jo1Bo9R5bRfZDsaVs1Q and I stay logged out.

Did the issue present with default Shields settings? (yes/no) Yes

Does the site function as expected when Shields are turned off? Yes

Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration. (yes/no): no but I have the youtube shorts blocked

Does the site work as expected when using Chrome? Yes

**Brave version (check About Brave): Brave 1.75.181, Chromium 133.0.6943.141
Android 15; Build/AQ3A.240929.001

@ptwabackup,
Can you please try clearing cache/site data for Youtube on your Android device and then try logging in again?

  1. Visit youtube.com
  2. Tap the “tune” icon to the left of the URL in the address bar
  3. Tap Cookies & site data
  4. Tap the “Trash” icon to clear data

Refresh the page and test again.

Just did, same it redirects to the same URL (channel Two on YouTube)

So that’s…really weird. To clarify, when you are redirected, are you logged in and just redirected to that page? Or are you only redirected to the page and not logged in?

If you open a Private browsing tab and try logging in, do you see the same behavior?

I m only redirected to the page and Not logged in.

The private browsing tab also does the exact same thing.

@ptwabackup would you be willing to test this in the Beta build of the app and see if it reproduces there? You can download the Beta from the app store and install/run it without interfering with your current installation.

So, what I did was uninstall brave and reinstalled it and the problem was solved lol. One thing though, now the phone screen sleeps off mid video which wasn’t the case earlier, any idea how to change that setting to fix it?

@ptwabackup,
Thanks for confirming. Glad it’s working now. Unfortunate that you are running into this other issue – fortunately the team does know about it and we’re working to get this resolved asap. Note that this issue does not effect all users: