Sorry, this video cannot be played.

[mills2533]

I had this working for a couple apps but now when I try to play a video it says "Sorry, this video cannot be played." This started happening today. Is anyone else having this issue?

[MonKy FoniKs]

Having the same issue now, out of the blue it stopped working. "Sorry, this video cannot be played."

[Naushad Kasu]

I am going to look into this issue but if anyone wants to tackle it that would be great. 

[Tom Ruys]

Same problem here, seemed to work before, reimplemented the code and now I get this error as well. "Sorry, this video cannot be played."

Logcat:

09-27 21:10:11.865: E/MediaPlayer(722): error (1, -1004)

09-27 21:10:12.185: E/MediaPlayer(722): Error (1,-1004)

09-27 21:10:12.185: D/VideoView(722): Error: 1,-1004

[mills2533]

I'm not sure exactly what parameters were provided/required in the past but I don't think the token info gives enough parameters to make the proper playback request.

When I sniff http packets using my computer the final playback request looks like this and it does play in Windows Media Player:

http://o-o---preferred---sn-jvhj5nu-qxol---v16---lscache8.c.youtube.com/videoplayback?cp=U0hTTVhOU19IUUNOM19QSFdGOmcwYUdvemJTaWU5&expire=1348835537&fexp=907605%2C923606%2C906520%2C914010%2C922401%2C920704%2C912806%2C927201%2C913419%2C913546%2C913556%2C919349%2C919351%2C925109%2C919003%2C912706&id=0baf2076d00ee2cb&ip=67.177.193.245&ipbits=8&itag=18&keepalive=yes&key=yt1&ms=au&mt=1348812313&mv=m&range=0-1413119&ratebypass=yes&signature=2F2B78225FCC724A5B11395B8428B1C5425E31A4.6735E851B21B6CD5F8C5A8A9E43FA2268D030370&source=youtube&sparams=cp%2Cid%2Cip%2Cipbits%2Citag%2Cratebypass%2Csource%2Cupn%2Cexpire&sver=3&upn=zhx2JhmW0ec

When debugging the app on a phone, the final playback request looks like this and does not play:
http://o-o---preferred---sn-jvhj5nu-qxol---v16---lscache8.c.youtube.com/videoplayback?upn=-gRIMIFXfL4&sparams=cp%2Cid%2Cip%2Cipbits%2Citag%2Cratebypass%2Csource%2Cupn%2Cexpire&fexp=909708%2C900157%2C900203%2C914041%2C922401%2C920704%2C912806%2C913419%2C913546%2C913556%2C919349%2C919351%2C925109%2C919003%2C920201%2C912706%2C900816&key=yt1&expire=1348831937&itag=18&ipbits=8&sver=3&ratebypass=yes&mt=1348811352&ip=67.177.193.245&mv=m&source=youtube&ms=au&cp=U0hTTVhOT19IUUNOM19QSFNKOmJZaWItMnN0ZWVu&id=0baf2076d00ee2cb

However, when I forced the app to use the top URL that worked on my computer, the app does play the correct video on my phone. So, what's the difference between the two? The good request has the following additional parameters: gcr, keepalive, range, and signature.

[Jeff]

I can confirm the same symptoms on an app that was previously working with OpenYouTubeActivity.  The URLs I am sniffing return a 403 error.  After searching around, I see that Google has announced a new YouTube android embed API, but not yet released it, so it makes me wonder if they've added some API key based authentication.  Any further insight from the group would be appreciated.

-jeff

[Anthony Sosso]

I'm not super sure because I haven't looked at the project source in a long long time, but I was doing some youtube-ish embedding stuff for mobile apps and independently noticed this breakage.  One fix for us was noticing that the "sig" parameter is now "signature", so if you're doing something involving the player parameters, I'd start looking there.

[Marty Miller]

Yes, I'm having the same problem.  Thanks for posting this.

[Timothy Graupmann]

I have the same issue. Looks like there's been no activity for a while. Is this project abandoned?

It really looks like a neat plugin. For now I'll fall back on a WebView....