[Android] Update `compileSdkVersion` to 28 and introduce `AndroidX`
See original GitHub issueAndroid had introduced sdk 28
with supporting libraries replaced by androidx
. Many maintained libraries, like com.theartofdev.edmodo:android-image-cropper
that we’re using have already made this migration. Unfortunately we’re unable to use them because of dependency hell that happens when we’re having different compileSdkVersion
.
Proposal: update compileSdkVersion
to 28 and replace all deprecated android-support-*
libraries with androidX
. Moreover some cleanup is advisable in gradle
files as well.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:5 (5 by maintainers)
Top Results From Across the Web
AndroidX releases | Android Developers
Maven Group ID Latest Update Stable Release Alpha Release
activity October 24, 2022 1.6.1 1.7.0‑alpha02
ads January 22, 2020 ‑ 1.0.0‑alpha04
annotation (*) September 21, 2022...
Read more >Why AndroidX needs compileSdkVersion set to be 28 or higher
I understand that AndroidX is simply a new upgrade to the support library which focuses on providing backwards compatibility for earlier ...
Read more >CompileSdkVersion and targetSdkVersion — what is the ...
In this article, we'll take a closer look at two values that are set in the build.gradle file: compileSdkVersion and targetSdkVersion.
Read more >How to Fix: The minCompileSdk (31) is greater ... - YouTube
... AAR metadata (META-INF/com/ android /build/gradle/aar-metadata.properties) is greater than this module's compileSdkVersion ( android -30).
Read more >AndroidX migration: what ,why, how? | by SHISHIR - Medium
Step 01: Set the compile SDK version to Android 9.0 (API level 28) or higher as minimum compile sdk version required for androidx...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Did this happen/is there some other tracking issue I can follow? Or is it dependent on https://github.com/facebook/react-native/issues/23112 and nothing for expo itself to do?
I’m closing this issue as it’s been solved already - we’ve migrated to AndroidX on master a few days ago: #5521, so the next SDK will use it 🙂