-
Notifications
You must be signed in to change notification settings - Fork 48
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
Type-forwarding for binding libraries #807
Comments
@JensSchadron Google moving types around problem is not new but we hit it more often in last 4-6 months (some libraries got Type forwarding is solution for API breakage in .NET world and it would help for cases like this one. Google is not that strict with their APIs:
Does Android native world has "type forwarding"? I am not aware of it. So, we are in the same situation as Android devs. Improvements (nice-to-haves) would be great, but I am not sure we'll be able to implement it very soon.
We'll discuss it, but... |
+1 here. @JensSchadron instead of binding lottie try to use SkiaSharp.Extened.UI |
This should be fixed with the latest version of
|
Android application type
Android for .NET (net6.0-android, etc.)
Affected platform version
.NET 8 RC2
Description
After having binded the
com.airbnb.android:lottie
android package, I stumbled upon an issue where the AOT compiler would crash due to not being able to resolve the assembly ofAndroidX.Collection
. After further investigation, I noticed that the binding library was bound using version 1.2.0.6 ofXamarin.AndroidX.Collection
while my consuming project was using version 1.3.0.1 of said package. However, since version 1.3.0 of said package, all types have been moved to theXamarin.AndroidX.Collection.Jvm
package, but (seemingly?) no type forwards have been set up on the original package, breaking all binding projects that had been compiled against an older version of the package.This all being said, I think this issue could be avoided by adding type-forwards on the binding library, but I'm not sure at all how feasible that would be.
Steps to Reproduce
Did you find any workaround?
Relevant log output
The text was updated successfully, but these errors were encountered: