-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Bump minSdk to 21 - Android 5 / Lollipop #7613
Conversation
There also resources in |
Thank you for the hint. |
Great! After a quick look at the code I've found other things that are unnecessary on API 21+:
|
Please also check whether we can disable Are you going to upgrade okHttp in this PR? |
Thank you guys for the hints, I will have a look.
No that should be a new one. I'm just dropping 4.4 here 😄 |
This is not possible. Fun Fact: Compiling works execution not
|
@litetex It just came to my mind that if you disable vector drawables backwards compatibility, you need also to replace |
When I don't replace the
Anyway, I replaced the usages now. |
Kudos, SonarCloud Quality Gate passed! |
Will there be a new seperate downloadable Legacy release for the last version that supported Android 4.4? Asking because when I'm checking the changelog and the version of the current Legacy release, there doesn't seem to be any indication in the changelog that there was a change in minSdk in version 0.20.9 ?.? |
This will only be required once a security issue is found in OkHttp 3.x, right? What I mean is, could we keep releasing new versions with Kitkat support until we are forced to upgrade OkHttp to 4.x? |
@opusforlife2 since OkHttp 3.x is now not supported anymore, it's just a matter of time before a vulnerability is found, and it would be difficult to know that a new vulnerability was found. So it is a good idea imo to just drop support for 4.4, upgrade to OkHttp 4.x and stay on the safe side |
This is indeed a cause for celebration! I can think of a few other compatibility things that can be removed, but they aren't that important. I can just create a PR for those if we do decide to go forward with dropping all legacy support (everything < 21, including NewPipe Legacy). |
In that case, considering that 19 PRs are already merged for the next version, maybe we should only merge this PR and release ASAP. |
This comment was marked as off-topic.
This comment was marked as off-topic.
47fea6e
to
4278844
Compare
app/src/main/java/org/schabi/newpipe/error/ReCaptchaActivity.java
Outdated
Show resolved
Hide resolved
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 mostly good to me
app/src/main/java/org/schabi/newpipe/error/ReCaptchaActivity.java
Outdated
Show resolved
Hide resolved
53bd586
to
f3c5cc6
Compare
@litetex Could I rebase this PR to fix the conflicts? |
@TacoTheDank Feel free to do so but note that this PR was create some months ago. |
9600dee
to
fc28e96
Compare
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.
@TacoTheDank
Are you finished with your changes?
If there is nothing additional to do I think we can merge the branch.
Are we done with all the stuff that was proposed to be merged before removing Kitkat support? I can't exactly remember what those things were, though I think DASH and new stream notifications were two of them. |
@opusforlife2 yes, we are done; there has been a recent discussion about whether to also wait for tex's DASH-2, but we decided not to wait any longer. |
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.
Took a look at the code, lgtm, thank you to everyone involved!
This comment was marked as spam.
This comment was marked as spam.
Yep, all done! |
I tested some misc things and could not find issues |
Kudos, SonarCloud Quality Gate passed! |
Isn't that purely the extractor? Extractor changes shouldn't have any influence on Legacy, no? I was under the impression that the front-end is what differs between NP and Legacy, which is why we wanted to add some critical front-end PRs before bumping. Is that not the case? |
@opusforlife2 no, DASH-2 will also require big front-end changes because the extractor API will be changing again |
What is it?
Description of the changes in your PR
21
- Android 5 / Lollipop - Dropped support for Android 4.4 and removed all corresponding code snippetsFixes the following issue(s)
APK testing
The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR.
Due diligence