-
Notifications
You must be signed in to change notification settings - Fork 39
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
Assembly 'Xamarin.Android.Support.v4' is using '[assembly: Java.Interop.JavaLibraryReferenceAttribute]', which is no longer supported. #112
Comments
Did you try bumping TargetFramework? |
yes, but if I change TargetFramework to v9.0 not v10.0 then it's normal, why? |
This has nothing to do with AndroidX. Something is pulling in Android.Support dependencies and this attribute is from Android.Support |
Just getting around to updating from 9 to 10 as the target and I'm seeing the same errors. Was otherwise reading and following along with the required changes in this article: https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/android/androidx-migration. |
I changed from 10 to 9 and it resolved. I just don't understand why? |
Updated all nugets, and had to pull the code for one of them directly in to the solution (https://github.com/EgorBo/Toasts.Forms.Plugin) because it's not being maintained...and somewhere in that process things are now building/running. |
@DennisWelu Geez these references are old like me: This is something we cannot predict and easily solve. |
@moljac LOL, well....I spoke too soon. We had updated the target SDK but forgot to update the "compile using" setting to match... And when that happened the errors returned. Problem solving is still underway - will update with more info when we know something further! |
We started to receive this error today after we upgraded to the latest Xamarin.Forms. However, it appears to be one of the plugins (Xam.Plugins.Notifier) that is still referencing Xamarin.Android.Support.v4. I have opened an issue for that project here: |
The XA0121 warning from Xamarin.Android 10.1 is now an error because compatibility with the old GetAdditionalResourcesFromAssemblies MSBuild task has been removed. Any project that uses one of the affected Xamarin.Android.Support libraries from version 26 or earlier will now see errors like: Copy |
Following up on my previous post, the other Nuget that we didn't realize was pulling in Android.Support dependencies was the ZXing library. Updated to use the Beta prerelease created earlier this year and that solved the problem. |
I had the same error message with Xamarin.Android.Support.CustomTab package, installing manually library in project solved the issue. |
Is there any fix or work around to this issue? My project was developed a long time ago and last built using VS 2017 and Target Framework 6, I have since updated to VS 2019 and have updated Xamarin.Forms to the latest version and the Target Framework to 9 (And 10) and am receiving the error:
|
It sounds like the available fixes are:
Google has deprecated the Android Support libraries in favor of AndroidX, so I would not expect to see any future updates to them. |
Wow!, I hit this error after updating all the nuget packages in the project. I'm using AndroidX, the last version of the Support libraries (28.x) and targeting v11.0 |
I can't tell you a specific fix, but I know the web of dependencies through the nuget packages can easily lead you to pulling in an unexpected older version of something. That's the best I can think of is to carefully go through that dependency tree and look for that situation. Wish I could help more! |
I'm having this problem with an Android Library which I'm migrating to Xamarin. I tried to remove all the packages with dependency on Android.Support.* libraries, but I'm still getting these errors. Is there a way to check which of my packages are dependent on the Support libraries? Or is it better to add the version 27 of the Android.Support libraries? I'd appreciate your help, I have no idea how to fix this, anymore. |
Closing this as the Android Support Libraries have been deprecated for ~3 years. The fix for this is to fully migrate to AndroidX and ensure that no Android Support libraries are referenced by your project or your project's dependencies. |
I reference #48 but not working
something wrong?
The text was updated successfully, but these errors were encountered: