-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[YouTube] Cache deobfuscation code and more fixes #447
Conversation
This comment has been minimized.
This comment has been minimized.
Do we have any DASH videos in our tests? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Thank you, that's reproducible. I'll look into it later |
Hi dEvS! Great App! Very nice!!11! New updare wHEN? :D |
I readded obfuscation code, and added caching for it: app-debug.zip |
This apk wants to install over the apk from your fix-detail-open branch. |
Oh, yes, I built it using that base code, hope that's not a problem ;-) |
Well, seeing as I'm testing both... it kind of is a problem. 🤐 |
So far it works fine. |
Seems to be working for me. Thanks. |
An apk containing both VideoDetailFragment fixes TeamNewPipe/NewPipe#4562 and deobfuscation improvements #447, in case someone (@opusforlife2) wants to test both at the same time: app-debug.zip |
b707faf
to
f1a982a
Compare
Wut bout seprate APK here? |
Why would you need that? Here you just need to test that all videos work, not if the app runs faster or whatever |
So I need an apk that is org schabi newpipe debug, or an apk named with this PR's branch name. The APKs you're uploading are named with the fix-video-details branch name, which is another actively updated PR I'm testing as well. So I need to be able to install them side by side. That's what I meant here #447 (comment). You were using the default debug name earlier. I still have that installed. (The one which crashes on DASH videos.) |
Here you are: app-debug.zip |
The video cannot be played with toast message "could not play this stream" Same issue #3336 ?! |
This comment has been minimized.
This comment has been minimized.
I cannot play videos that were previously broadcast live.
it happens with me only with this apk
Does not happen on the apk provided in the first comment. |
@opusforlife2 that's caused by updating to java 8 and will be fixed by @Isira-Seneviratne |
Ah, you're right. I was just assuming that since video details opened fine there was no error. But yeah, trying to play previously live streams fails with that toast. However, currently live videos play fine, @Stypox. |
f1a982a
to
f9ad46f
Compare
@xibr @opusforlife2 I fixed problems with livestreams by reverting the way they are detected:
The two APKs have the same extractor implementation, so test only one of those. If you choose the first one you can test both this changes and those in TeamNewPipe/NewPipe#4562 at once. |
Fix age restriction extraction Automatically fixes more things
f9ad46f
to
89a77ae
Compare
no issues about parse date now, and live streams problems work as well. |
Yup. All 3 kinds of videos work: live streams, previously live streams, and normal videos. |
This fixes TeamNewPipe/NewPipe#3336, I tested with a livestream that had just ended and, even though such streams are still considered as running livestreams (which are played as DASH by the NewPipe player), there are no errors anymore since the DASH url is extracted correctly and such videos are detected correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Next time, please make more commits, E.g. "Automatically fix more things" and "fix age restriction extraction" could have been in separate commits. That speeds up the review process.
YouTube's changes :-D :-DApparently YouTube stopped providing obfuscated URLs completely! This solves many problems in theYouTubeStreamExtractor
, since now there won't be any "could not deobfuscate ..." exception and loading will be much faster. I don't know the reason for this change, but I ran everyYouTubeStreamExtractor*Test
more than 50 times each, all without errors :-D. Btw, this PR also includes (as a standalone commit which should then be squashed, as it does not make sense) my first attempt at speeding up the fetching process, i.e. caching player urls, which are now not needed anymore at all.In more detail:
onFetchPage()
, but only when requestedinitialAjaxJson
assertNotNull
on related streams if they are expected inDefaultStreamExtractorTest
Fixes
Testing apk
Since I don't know whether this change is there all over the world, here is an apk for all of you to test. Please try to test it under many different network conditions.
app-debug.zip
@opusforlife2 could you link here users that encountered problems with youtube streams in 0.20.1? So that we have many people to test this ;-)