-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Release v0.16.2 #2312
Release v0.16.2 #2312
Conversation
Add dunction handleText() for #1951 issue
fix invalid channel url for commends
Fix AudioManager memory leak
added top padding for comments and related videos
Small ux improve
Currently translated at 100.0% (443 of 443 strings)
Fixed CheckForNewAppVersionTask being executed when it shouldn't
Currently translated at 100.0% (443 of 443 strings)
I have test this release, and it work Well! Thanks for your work :) |
Correct me if I'm wrong but I think the Close button when a video ends doesn't work as intended. To elaborate:
The video will start over on the popup player. Is that how it's supposed to work? |
Nice catch. @nv95 do you have time to look at it? |
Currently translated at 98.6% (437 of 443 strings)
Currently translated at 99.5% (441 of 443 strings)
Currently translated at 100.0% (443 of 443 strings)
Currently translated at 100.0% (443 of 443 strings)
Currently translated at 100.0% (443 of 443 strings)
@Artuist Thanks for reporting. I tried to track this down, but unfortunately, this is wrong behaviour is not limited to the close button, but to all player exit actions when minimize to background/popup is enabled. I first tried to find any related code which has been touched during the work on this release. After debugging and searching for too long, it turned out that this bug existed in previous versions, too. Whenever a video is left by either closing it or switching to a different player, the player to minimize to is opened. For example, set minimize to background, open a video and than switch to popup. Both players will be started. Therefore, I wouldn't see this as a blocker for this release. nevertheless, we should open a ticket. @theScrabi AFAICS only the weblate update is missing to get this release out to the people. |
Currently translated at 100.0% (443 of 443 strings)
Currently translated at 100.0% (443 of 443 strings)
Thanks to @Stypox, we can ship two more fixes with 0,16.2:
Here is the new RC: newpipe_0.16.2_rc2_debug.apk.zip |
Currently translated at 96.8% (429 of 443 strings)
Currently translated at 100.0% (443 of 443 strings)
Currently translated at 99.8% (442 of 443 strings)
Update translations
Remove strings which have been deleted from the English strings file during development, but were translated via Weblate, which failed to pull and push our upstream repo.
I see. You can add @TobiGr did I forget to document this? |
Yes, please. It's been too long. We are almost at June. |
@theScrabi No, I just didn't see it at first |
We should release bug fixes from time to time... :)
newpipe_0.16.2_rc2_debug.apk.zip (by @TobiGr)
Please report crashes and bugs in #2314
Changelog
Improvements
Fixed
ToDo