locked
Android Build Failure After Upgrade Xamarin Forms From 4.7 To 4.8 RRS feed

  • Question

  • User396490 posted

    Hello,

    This morning I updated an existing app to use Xamarin.Forms 4.8.1269,, after the update the app would no longer build for Android. The following error appears : "Assembly 'Xamarin.Android.Support.v4' is using '[assembly: Android.IncludeAndroidResourcesFromAttribute]', which is no longer supported. Use a newer version of this NuGet package or notify the library author"

    After googling about the issue, I have updated the Android Project to the target the latest api which api 30. I have also updated all nuget packages to the latest version, this also include the latest version of visual studio.

    I am not sure how to resolve this issue and if any has seen or fixed this issue any assistance would be greatly appreciated.

    System Build

    Microsoft Visual Studio Community 2019 Version 16.7.2 VisualStudio.16.Release/16.7.2+30413.136 Microsoft .NET Framework Version 4.8.03752

    Installed Version: Community

    Xamarin 16.7.000.440 (d16-7@358f3c6) Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

    Xamarin Designer 16.7.0.495 (remotes/origin/d16-7@79c0c522c) Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

    Xamarin Templates 16.7.85 (1bcbbdf) Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

    Xamarin.Android SDK 11.0.2.0 (d16-7/025fde9) Xamarin.Android Reference Assemblies and MSBuild support. Mono: 83105ba Java.Interop: xamarin/java.interop/d16-7@1f3388a ProGuard: Guardsquare/proguard/proguard6.2.2@ebe9000 SQLite: xamarin/sqlite/3.32.1@1a3276b Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-7@017078f

    Xamarin.iOS and Xamarin.Mac SDK 13.20.2.2 (817b6f72a) Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

    Thursday, August 27, 2020 1:44 PM

All replies

  • User396490 posted

    This morning I have rolled back the Xamarin.Forms package to the previous version 4.7.0.1260 and the issue is now gone.

    Friday, August 28, 2020 8:12 AM