-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Android SDK BuildToolsVersion and compileSdkVersion update implication #332
Comments
Ping @lucasbento |
any updates on this? I am unable to use react-native-svg - error:
|
At least I'm able to use v25 just fine in both dev and prod builds. Have you tried opening the android project in android studio and install v25? |
am able to use v25 too.. just bothers me that react native suggests to use v23 |
Am I missing something? Seems like big issue to force people off the version that RN requires for a RN lib. |
How is it an issue? Or a requirement? More like an outdated suggestion from their part. E.g. react-native-fbsdk use SDK 26 and appcompat-v7:27.0.2 |
Guess I just assumed that if they explicitly said version 23, they must have at least some reasoning behind it. Not well versed in the implications of changing sdk versions, so really wasn't looking to mess with the defaults if at all possible. RN not the most stable environment ever as is. |
That's true. But at least I've been running (all?) the newer version without issues, as long as the appcompat matches. |
I've made a PR to react-native and the docs. So now you have a source telling you to upgrade, to address a Path Traversal Vulnerability.
|
@hrm123 @nol13 @Maxwell2022 I've released a new version, which aligns with react-native init, to make it as easy as possible for newcomers. Anyone with needs to upgrade any versions to anything different from that, will hopefully learn how to change them in their dependencies in the process as well. Lets see if they upgrade any versions, now that a PR exists. Can release a new version to align with that when they do. |
It seems facebook themselves are running appcompat 27.0.2 internally, which i guesss means they compile against SDK 27. I think manually updating these versions to the latest ones, is the way to go, for anyone who wants to use the latest patches for security, performance etc. Using outdated versions because some more than one year old documentation suggests so, probably shouldn't be best practice. Especially when up to date sources explicitly say to use the latest available. Keeping it maximally convenient for beginners makes sense as well, thus having react-native init use the latest ones is what should actually change. |
I have been getting this error message and have been unable to make it go away, no matter what I tried. In the end, downgrading |
@Billy- Interesting, they should be aligned with react-native in the latest version. Can you provide your android/app/build.gradle file? The appcompat dependency has been removed as well, so it should build with almost any combination now. |
Unfortunately I have opted to go without shadows (this was being installed as a dependency of react-native-shadows) for now - but will revisit it later. However, here is our gradle file, it has mostly been reverted back to what was being used before I started trying to get this to work. android/app/build.gradle
|
I've noticed that 2 months ago the version of the
buildToolsVersion
has been bumped from23.0.1
(required version from react-native docs) to25.0.1
, as well as thecompileSdkVersion
from23
to25
The React Native docs specifically says:
Someone also tries to submit a PR to react-native project that got rejected with the following comment:
I'm not sure what is the implication of this and just want to raise it here.
Here is my original comment on the commit:
47a79d3#commitcomment-22096489
The text was updated successfully, but these errors were encountered: