You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
all is functioned. Wiith the new PlayerApiRequest options i receive only Video without an signatureCipher, even on MusicVideos. I have used old youtube url from issues to test the new signature cipher.
I use the MWEB Client to receive signatureCipher Links and the decoded string are not viewable. Are this old sigs, while MWEB?
It was only a test and the MWEB Client the only chance to receive decoded videos-links?
Has anyody an cipherencoded url for me that reponse signatureCipher-urls with the new Android-Client? THat i can test the new SigntureDecoder Class?
thx
Edit: Tested on https://www.youtube.com/watch?v=suAR1PYFNYA SignatureDecoder don't functioned on this link with MWEB Client???? Has Youtube changed something? Why only MWEB produces signatureCipher-Links?
This are my Fix too become ultralow formats, only as an test of the new SignatureDecoder Class.
Hello,
all is functioned. Wiith the new PlayerApiRequest options i receive only Video without an signatureCipher, even on MusicVideos. I have used old youtube url from issues to test the new signature cipher.
https://youtu.be/72oON3ChgPc
I use the MWEB Client to receive signatureCipher Links and the decoded string are not viewable. Are this old sigs, while MWEB?
It was only a test and the MWEB Client the only chance to receive decoded videos-links?
Has anyody an cipherencoded url for me that reponse signatureCipher-urls with the new Android-Client? THat i can test the new SigntureDecoder Class?
thx
Edit: Tested on
https://www.youtube.com/watch?v=suAR1PYFNYA
SignatureDecoder don't functioned on this link with MWEB Client???? Has Youtube changed something? Why only MWEB produces signatureCipher-Links?This are my Fix too become ultralow formats, only as an test of the new SignatureDecoder Class.
is MWEB depreceated?
The text was updated successfully, but these errors were encountered: