Closed abhishekBansal closed 6 years ago
I am not too deep in the Android development world, but would you mind explaining the build errors that you got?
Sure
compile
and testCompile
are now deprecatedtargetSDK
, compileSDK
and buildToolVersions
were too old to be compiled with Android Studio 3.1+Google
maven repositoriesOk, that makes sense, thank you. I am only wondering if it was necessary to change the minSdkVersion
for the library and example? Could this change lead to build failures for library users?
So min SDK version had some discrepancy, library minSDK version was 4 while application minSDK version was 7. Applications can/should not have min SDK version higher then library.
Keeping minSDK 14
is pretty safe as 99.5%
users are on Android devices that have SDK versions 15+
as you can see here
https://developer.android.com/about/dashboards/
Ok, but can we also keep the minSdkVersion
at 7? I don't think we need any features that are available for the api version 8+. I am well aware that this will increase the share of supported android devices not significantly but I don't see a reason to bump the minimum SDK version without an actual need for it. What do you think?
So com.android.support:appcompat-v7:27.1.1
declares minSDKVersion
as 14
. This will still fail ManifestMerger
step in build process. I would strongly recommend keeping SDK version 14 as Android Studio
itself suggests incrementing it to 14 when set to 7.
That makes sense. I had to update the Android SDK version in the .travis.yml file but now it's merged, thank you
…s gradle parameters