-
Notifications
You must be signed in to change notification settings - Fork 153
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
Target api 35 #3776
Target api 35 #3776
Conversation
Tested OK on a API 35 emulator.
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
Quality Gate passedIssues Measures |
We may have to check:
Could this allow us to remove some localazy post-processing?
The last 2 may be closely tied to the Element Call integration. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3776 +/- ##
========================================
Coverage 82.97% 82.97%
========================================
Files 1770 1770
Lines 44422 44422
Branches 5222 5223 +1
========================================
Hits 36858 36858
Misses 5729 5729
Partials 1835 1835 ☔ View full report in Codecov by Sentry. |
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.
I took another look, tested it a bit and I think we're handling all the changes I mentioned above.
Content
Change compile and target to 35 and fix new warnings in the code. I do not think that we need to take special action for the change about foreground service (see https://developer.android.com/about/versions/15/behavior-changes-15#fgs-hardening). I do not see in https://developer.android.com/about/versions/15/behavior-changes-15 other actions that we should handle.
Also improve code quality on the
Versions
object.Motivation and context
Be up to date and allow dependencies to be upgraded (see for instance #3766)
Screenshots / GIFs
Tests
Tested devices
Checklist