YouTube bot check after stream request

[calirep]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.
• I have read and understood the AI policy. The content of this bug report is not generated by AI.

Affected version

0.28.5

Steps to reproduce the bug

I use Cape phone service on grapheneOS with always active VPN(mullvad) 😂
Works great most of the time but every now & then it gives an error for "login request from YouTube." I usually just change my Location and it works after that but figured I'll add my logs.

Expected behavior

No response

Actual behavior

No response

Screenshots/Screen recordings

No response

Logs

Exception

• User Action: requested stream
• Request: https://www.youtube.com/watch?v=xSdT42WSr7I
• Content Country: US
• Content Language: en-US
• App Language: en_US
• Service: YouTube
• Timestamp: 2026-04-25T18:59:27.035-07:00
• Package: org.schabi.newpipe
• Service: YouTube
• Version: 0.28.5
• OS: Linux Android 16 - 36

Crash log

org.schabi.newpipe.extractor.exceptions.SignInConfirmNotBotException: YouTube probably temporarily blocked anonymous watch access with this IP , got error LOGIN_REQUIRED: "Sign in to confirm that you're not a bot"
	at org.schabi.newpipe.extractor.services.youtube.extractors.YoutubeStreamExtractor.onFetchPage(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:380)
	at org.schabi.newpipe.extractor.ListExtractor.fetchPage(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:25)
	at org.schabi.newpipe.util.ExtractorHelper$$ExternalSyntheticLambda3.call(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:141)
	at io.reactivex.rxjava3.internal.operators.single.SingleAmb.subscribeActual(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:38)
	at io.reactivex.rxjava3.core.Single.subscribe(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:1)
	at io.reactivex.rxjava3.internal.operators.single.SingleDoOnEvent.subscribeActual(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:17)
	at io.reactivex.rxjava3.core.Single.subscribe(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:1)
	at io.reactivex.rxjava3.internal.operators.single.SingleSubscribeOn$SubscribeOnObserver.run(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:5)
	at io.reactivex.rxjava3.core.Scheduler$DisposeTask.run(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:10)
	at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.run(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:22)
	at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.call(r8-map-id-eeb60bc7eafd7d14a24650eafbfe8b4ce497b5ec4b44d8fb117249d53eb0f7fa:1)
	at java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:348)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
	at java.lang.Thread.run(Thread.java:1563)

---

Affected Android/Custom ROM version

Android 16 / GrapheneOS

Affected device model

Pixel 9a

Additional information

No response

[ShareASmile]

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.

Please search (at least) for duplicates first before opening an issue, especially check from pinned ones. I literally searched for "bot checks" and got the linked issue in one go. Anyway, if you make a little more effort when checking for duplicates, it saves everyone time specially of developers & maintainers. Thank you.

[calirep]

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.

Please search (at least) for duplicates first before opening an issue, especially check from pinned ones. I literally searched for "bot checks" and got the linked issue in one go. Anyway, if you make a little more effort when checking for duplicates, it saves everyone time specially of developers & maintainers. Thank you.

Yeaaa I'm not going to be putting in much EXTRA effort for that type of stuff. Didn't see a linked issue my first look and wasn't going to go over each issue either but your welcome.