I am upgrading mapbox version from 7.x to 8.x. On the gradle files, there is also 'com.mapbox.mapboxsdk:mapbox-android-services:2.2.9'
Should this be upgraded to latest version too? If yes, could somebody help me the find the migration guide or is it not needed?
7.x to 8.x did not bring any breaking changes in the APIs, the only change being the pricing. mapbox-android-services is long deprecated, you should use Mapbox Java SDK instead.
Related
the google play console advised me to use the debugSymbolLevel option, but it seems that requires a higher gradle plugin version(4.1). Currently my Android Gradle Plugin Version is 3.5.4 and my Gradle Version 5.6.4
I know very little about gradle. Is there any reason i shouldn't just select the highest versions for both? If yes which ones should i use?
Android Gradle Plugin Version offers options up to 7.3.1
Gradle Version upt to '8.0-milestone2'
Since the two versions span a lot, there might be a lot of breaking changes for your project. I suggest you doing some backup, trying to choose a stable version of it (7.x) and running the project. Good luck.
Is there any minimum recommended or required Gradle or Gradle Plugin versions if we intend to target Android 30?
You can have reference to this https://developer.android.com/studio/releases/gradle-plugin
It is always best to use the latest Gradle and AGP, if you're using Beta or Canary distribution, back down one small version if you encounter errors when compiling.
I am using firebase in my android app. I have added firebase-messaging, firebase-database, firebase-auth, and firebase-storage libraries to my build.gradle.
When a new version of these libraries is available, Android Studio suggests to update the version to the new one.
But, the problem is that the latest versions of these four firebase libraries are not the same. Following were the versions when I last updated them to the latest version
My question is, if I update the firebase libraries to the latest versions available at a certain time, are they compatible with each other? Is it OK to update the library versions to the latest without doing any further investigations about the version compatibility?
The latest versions of everything should be compatible with each other. You can see them all listed in the documentation. The Play services gradle plugin will check to see if there are any possible incompatibilities between versions.
Line with yellow highlight you can see warning, they describes the latest library, and yes when firebase firm put library for end developers they also consider the old version features and other stuff, means they doesn't remove all features but they includes new features with new one version, so that is ok and no need to worry about updating a new version of firebase libraries.
say there is a newer version of 3rd party dependency released. How does our Android Studio be notified?
For gradle, they recommend to build against exact versions.
But you can write it like below to use latest library version
compile "junit:junit:4.+"
"But the + is not recommended because it can break builds when libraries depend on each other and use different versions."
Check this. it may help you.
Gradle plugin to discover dependency updates
https://github.com/ben-manes/gradle-versions-plugin
I remember Google says we should always use the latest API and set the min sdk to lower version.
My question is, If I use compatibility package, what Android SDK version should I use? If I use 4.0, will there be conflict? Thanks,
You should still be targeting the latest SDK. Make sure that you use the compatibility package imports and not the SDK imports.