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.
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.
I am using firebase in my android app, and I had included several firebase client libraries in my build.gradle, each by its own version.
When a new version of each library was available, Android Studio suggested me to upgrade the version to the newer version by highlighting the dependency in yellow.
I recently updated my build.gradle to use Firebase BOM, so that the BOM picks the compatible versions of the each firebase library, so I don't need to specify individual versions of each firebase library.
implementation platform('com.google.firebase:firebase-bom:26.1.0')
Now, Android Studio doesn't detect new versions of firebase-bom, like it did for individual firebase libraries earlier. For an example, I can see that 26.1.1 of firebase-bom is released, but Android Studio doesn't show me that.
Why is this? Is there any way to get Andriod Studio to detect new versions of firebase-bom?
I'm learning flutter. The "Adding Firebase to Flutter" tutorial shows to use this; "com.google.gms:google-services:3.2.1" but the latest version seems to be 4.2.0
Also, I'd like to use suitable (latest?) version of packages from https://pub.dartlang.org/packages
Such as (currently):
firebase_core 0.3.1+1 and
google_sign_in 4.0.1+1
If I just choose the latest numbers I get a lot of compilation errors.
My Questions is: where can I find the latest supports/compatible version numbers for these various components?
The only thing I have found to work is to use:"com.google.gms:google-services:3.2.1" and to just keep downgrading pub package versions numbers until the compiler errors go away. I feel like there must be a more sane way to deduce the correct version numbers to use for various components.
Anybody have any insight into this issue?
Thanks
I need to see error messages but it's probably about AndroidX. If you have to check the changelog files of your plugins (by the way it's a good practice since sometimes readme's are not updated), you will probably see
Breaking change. Migrate from the deprecated original Android Support Library to AndroidX. This shouldn't result in any functional changes, but it requires any Android apps using this plugin to also migrate if they're using the original support library.
google_sign_in 4.0.0 changelog
You can avoid AndroidX by using these packages listed or you can migrate to AndroidX with these instructions.
flutter create is not coming with androidx, it comes with android support libraries, but if you have Android Studio, it's easy to migrate it. In my case, I've migrated it.
We have a Xamarin.Forms application which uses quite a few packages.
When building, we're getting hundreds of XA0106 warnings like this one:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(2,2): Warning XA0106: Skipping Musterd.Droid.Resource.Attribute.MediaRouteControllerWindowBackground. Please check that your Nuget Package versions are compatible. (XA0106) (Musterd.Droid)
I know that this is because of mismatches between support libraries used by packages. The problem is finding out which one(s)!
Is there any tool or build setting I can use which will help me home on which packages are causing this and so which I can/should update?
This can happen when the version of the Android SDK you are using is different to the version of the Android support packages used by your app. The support packages are versioned in a way that should match the compile time Android SDK.
The best fix is to always use the latest of both.
Update your Android SDK to have the latest stable installed.
Make sure your app compiles against the latest version in the project settings.
In the Android project update all NuGet Packages that start with Xamarin.Android to the latest version.
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