Replies: 1 comment 1 reply
-
|
There's nothing wrong with the Microsoft-published binding packages for Android. However, using them tends to introduce developers to the frustrating world of Android dependency management in .NET, which is what I'd guess is what you're referring to. I won't get into the 'why' behind this here, because it's discussed well elsewhere. But the punchline is that, many Android .NET apps, it's going to be your responsibility to explicitly manage the nuget package versions for a lot of your transitive dependencies. For .NET 10, I have this section in my .csproj to accomplish this currently: One noteworthy thing that comes up using Firestore specifically is that Xamarin.Protobuf.JavaLite package. Essentially, there's a bug in native dependency versions > 4.26.1. Native Android developers can work around it by pinning 4.26.1, but some NuGets in the .NET ecosystem make that not an option for us because they don't have matching version constraints. So I work around that by copying the .AAR file from 4.26.1 into the nuget cache for 4.30.2.2. It's messy, but it works. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I only wanted to thank you for keeping the Firebase packages for iOS up to date.
🎁
What do you use for firebase Android ? I have difficulties getting firebase to build on Android. I finally found a combination of older nugets starting from "Xamarin.Firebase" that work. But it would be better if all the latest nugets do work as expected 😁
Beta Was this translation helpful? Give feedback.
All reactions