XamarinComponents: Warning XBD100: XamarinBuildDownloadRestoreAssemblyAar is no longer supported

After updating to Xamarin.Build.Downloads 0.8.0, I now see the following warning on every build of my app:

3>C:\Users\mfeingol\.nuget\packages\xamarin.build.download\0.8.0\buildTransitive\Xamarin.Build.Download.targets(98,3): warning XBD100: ItemGroup `XamarinBuildDownloadRestoreAssemblyAar` is no longer supported.  If your build is failing, revert to an older Xamarin.Build.Download version, or migrate your packages to use the new `XamarinBuildDownloadAndroidAarLibrary` ItemGroup.  If your build is succeeding it is safe to ignore this warning.

cf https://github.com/xamarin/XamarinComponents/pull/774/files#r362907122 cc @mattleibow

Two questions:

  1. Is there anything I can do to get rid of this error? I’m not explicitly using XamarinBuildDownloadRestoreAssemblyAar anywhere that I’m aware of.
  2. If not, could the warning be disabled in cases where there’s no action item?

Thanks.

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Reactions: 34
  • Comments: 44 (3 by maintainers)

Most upvoted comments

This is still an issue with Xamarin.Build.Download version 0.10.0.

Any chance the warning could be either made actionable or removed?

Thanks.

Keep seeing this. Visual Studio 2019, Update 16.10.0

2021-05-31

In almost all cases, the warning from XBD is insignificant. It’s mostly caused by the fact GPS/FB basically supports both the newer way of automatically downloading and referencing .aar’s directly at build time as well as the old way of embedding them back into the .dll at build time.

At this point I think it’s safe we can remove the old method which unnecessarily causes the warning. I’ve started a PR here: xamarin/GooglePlayServicesComponents#392

When will there be an update for the Xamarin.Build including this?

In almost all cases, the warning from XBD is insignificant. It’s mostly caused by the fact GPS/FB basically supports both the newer way of automatically downloading and referencing .aar’s directly at build time as well as the old way of embedding them back into the .dll at build time.

At this point I think it’s safe we can remove the old method which unnecessarily causes the warning. I’ve started a PR here: https://github.com/xamarin/GooglePlayServicesComponents/pull/392

The warning for XamarinBuildDownloadRestoreAssemblyAar is actually saying that you have updated the XBD, but not the Play/Firebase libraries.

@mattleibow, which version of the Play/Firebase libraries will silence this warning?

I reverted “Xamarin.Firebase.Messaging” to 71.1740.4 and it works without errors. it is easy to find dependencies from NugetPackage manager. If you find that it depends on Xamarin.Build.Download >=0.10.0 then choose lower version of nuget package

I’m going to ping on this issue again. @Redth? @mattleibow? It would be great to no longer see this warning on every build.

My understanding is that it’s going to need a change from @Redth or @mattleibow. Perhaps one of them could explain?

But, to talk on the original issue…

The warning for XamarinBuildDownloadRestoreAssemblyAar is actually saying that you have updated the XBD, but not the Play/Firebase libraries. The warning is just saying that it found the old way of doing something that was unreliable. The new way is improved, but the various packages need to update. However, it is just a warning as the old way is sort of converted to the new way so no loss of data/functionality occurs.