search

TeamNewPipe / NewPipe-legacy

NewPipe with support for older devices
GNU General Public License v3.0
131 stars 36 forks source link

request on when a future update of the legacy version of newpiepe will arrive #72

Open ghost opened 3 years ago

ghost commented 3 years ago

I appreciate the work you have done to bring NewPipe to older devices like mine, I would like to ask you when an update will be released to the latest versions of NewPipe which contain many bugfixes to the problems reported by other legacy users such as the trend section not loading, comments not loading, also a problem has been fixed affecting EU states like mine.

Here is a brief summary of the changes/improvements made

v0.20.9 released on 13 Feb

Fixed

v0.20.10 released on 14 Feb

New

Improved

Fixed

Development

Localization

v0.20.11 released on 5 Mar

Improved

Fixed

And all the fixes from NewPipeExtractor v0.20.11

Development

Translation

v0.21.0 released 16 days ago

New

Improved

Fixed

Development

v0.21.1 released yesterday

Fixed YouTube not working properly in the EU. This was caused by a new cookie and privacy consent system which requires NewPipeExtractor to set a CONSENT cookie. TeamNewPipe/NewPipeExtractor#600

I have seen that version 0.21.2 will be released soon you can see the changelog in advance here, at this point I assume you will wait for the new 0.21.2 to merge everything.

Thanks for all the work, have a nice day.

XiangRongLin commented 3 years ago

I can't speak on when a new legacy version will be released. But i am regularly updating the v0.19.8 NewPipe version to the latest extractor version, which can be found here. https://github.com/TeamNewPipe/NewPipe/issues/4918

I can't confirm that it actually works on old devices, since no one confirmed it for me and i don't have one.

You won't be getting the new features there, but existing ones that are fixed in the Extractor will be fixed there too. Like the eu consent cookie bug

ZacharyFoxx commented 3 years ago

I can't speak on when a new legacy version will be released. But i am regularly updating the v0.19.8 NewPipe version to the latest extractor version, which can be found here. TeamNewPipe/NewPipe#4918

I can't confirm that it actually works on old devices, since no one confirmed it for me and i don't have one.

You won't be getting the new features there, but existing ones that are fixed in the Extractor will be fixed there too. Like the eu consent cookie bug

https://github.com/XiangRongLin/NewPipe-preuinified/issues/1

Apparently your release has a old bug which was fixed on legacy 20.8.

tossj commented 3 years ago

I've also been working on copying over commits from NewPipe to NewPipe-legacy in https://github.com/tossj/NewPipe-legacy/tree/update-newpipe-extractor-0.21.1

drogga commented 3 years ago

@XiangRongLin , @tossj - Since (@)friendlyanon seems to no longer be interested in working on this, I would like to test (on old bricks) your "Legacy" forks when they are ready, with latest bug fixes applied and the release builds compiled (I prefer to not use 'debug' builds, nor having to compile myself), ...just waiting for .apk(s) to test... ;) Thanks in advance.

Edit: There's also https://github.com/sh000gun/NewPipe-legacy/releases

ghost commented 3 years ago

@XiangRongLin I've been testing your fork for 3 days now, everything works perfectly on the youtube side, I suggest you put a warning for the legacy version that says not to open media.cc.de and Bandcamp because the app crashes and even reopening the app crashes creating a loop and you have to delete all the app data (luckily for me I had a backup of all the recent settings and I was able to load everything); soundcloud and Framatube don't load showing a connection error, the app doesn't crash for these two services. I thank you for supporting the legacy version, the app works perfectly for me since I only use newpipe for youtube.