futo-org / grayjay-android

Read-only mirror of Grayjay repo for issue tracking
https://gitlab.futo.org/videostreaming/grayjay
Other
754 stars 48 forks source link

YouTube: invalid iOS source response #1275

Closed vladimmi closed 3 days ago

vladimmi commented 2 months ago

What happened?

When I play any video and bot detection fallback was used, video only plays first minute or less. After that (or even quicker, just trying to rewind somewhere ahead) "Invalid iOS source response" message appears and video restarts.

Grayjay Version

253

What plugins are you seeing the problem on?

Youtube

Plugin Version

193

When do you experience the issue?

Relevant log output

No response

Graves-Aedan commented 2 months ago

I've been having this issue too, it started happening on a previous plugin version and we promptly got an update which gave us the additional message "Invalid iOS source response", but it didn't seem to fix the issue. If I can figure out why logging isn't working (I think that's a me problem) I'll update this comment with log info

EDIT/UPDATE: I turned my VPN off (Express VPN) and it started working. It still give the first "Using iOS Sources fallback (cached)" message, but none of the others. The video plays just fine and doesn't say anything about a block attempt.

Adriel3233 commented 2 months ago

I've also have the same issue, it started happening a few hours ago and when play the video gave us the additional message "Invalid iOS source response", but it didn't seem to fix the issue, and it restarts back to the beginning of the video.

madpete76 commented 1 month ago

Also suffering from this with YouTube, started a couple of weeks ago, the app is fully upto date and the plugin is now 196, but it's been the same problem on previous plugins too.

I reinstalled the plugin, but it didn't help.

FoolHen commented 3 weeks ago

Same here, can confirm that turning off the VPN fixes it.

support-grayjay commented 3 days ago

This seems to be fixed in latest version (209) of Youtube. Feel free to open a new issue if you are still encountering this.