Skip to content
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.

Warning XBD100: XamarinBuildDownloadRestoreAssemblyAar is no longer supported #784

Open
mfeingol opened this issue Jan 11, 2020 · 44 comments

Comments

@mfeingol
Copy link

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.

@coosmiyn
Copy link

I also have the same problem.

@Felsington
Copy link

I had this problem too. After I downgraded nearly all my plugins (e.g. xamarin.forms, googleplayservices.base and Xamarin.Build.Download) it works again for me.

@jdumasleon
Copy link

I also have the same problem with Xamarin.Build.Download 0.8.0, Xamarin.Forms 4.5 and last stable version packages of GooglePlayServicesComponents

@DevEddy
Copy link

DevEddy commented Mar 3, 2020

Same here

@cfl777
Copy link

cfl777 commented Mar 20, 2020

Same issue here, after upgrading to 0.10, but also got a 48 other errors:

e.g.
Resources/drawable-hdpi-v4/abc_textfield_default_mtrl_alpha.9 2.png : error APT2219: file name cannot contain '.' other than for specifying the extension.

@mattleibow
Copy link
Collaborator

@cfl777 I may be wrong, but this may be because you need to switch to the new d8 and r8 tools instead of the old (and soon-to-be-removed) dx and proguard. Try changing those in the project settings.

@cfl777
Copy link

cfl777 commented Mar 20, 2020

@mattleibow Appreciate the advise!

The problem I have though is that i get these issues when trying to use d8+r8:
R8 : warning : Missing class: com.android.tools.lint.detector.api.Detector
R8 : warning : Missing class: com.android.tools.lint.detector.api.Detector$UastScanner
R8 : warning : Missing class: com.android.tools.lint.client.api.IssueRegistry
R8 : error : Compilation can't be completed because some library classes are missing.

Only solution I could find online that comes close to the above is adding the below to Manifest:

    <uses-library android:name="org.apache.http.legacy" android:required="false" />

But that doesn't work for me, still trying to figure out what else i can try.

@mattleibow
Copy link
Collaborator

@cfl777 Is it possible to attach a build log? or a binlog?

@mattleibow
Copy link
Collaborator

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.

@cfl777
Copy link

cfl777 commented Mar 20, 2020

@mattleibow Sure no problem - will slack you the logs the second I get a chance.

That makes sense, will up my play/firebase libraries. Was just weird that I got those 48 other issues all of a sudden after updating Xamarin.Build.Download, so thought it was connected. But after multiple cleans/rebuilds etc those 48 issues disappeared.

Thanks for your help! :)

@mfeingol
Copy link
Author

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?

@mfeingol
Copy link
Author

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.

@JesperNJessen
Copy link

@mfeingol I recently updated my Firebase and other libraries and the warnings persist. I suspect we will need to wait for an update for Xamarin.Build or any number of Firebase libraries before this is resolved

@mfeingol
Copy link
Author

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

@mfeingol
Copy link
Author

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

@logeshpalani33
Copy link

How we can solve this

If your build is failing, revert to an older Xamarin.Build.Download version, or migrate your packages to use the newXamarinBuildDownloadAndroidAarLibrary ItemGroup. If your build is succeeding it is safe to ignore this warning.

@SoureMaster
Copy link

Yea, I need to find out how to solve this issue as well.

@chrisjmartinez
Copy link

This is happening once again on Visual Studio for Mac (community) on version 8.7.8 (build 4)
Xamarin.Build.Download 0.10.0
Cannot downgrade to XBD 0.9.0 as several packages have dependency on 0.10.0

@mfeingol
Copy link
Author

Another ping on this for @Redth and @mattleibow.

@wojciech-kulik
Copy link

+1

@XamarinInfo
Copy link

Hi,

I am facing the same issue here after restoring my mac OS.
Downloaded the latest visual studio project. I am trying to bulid the project which was successfully running in my system before OS restore.
Now I am not able to run it on my mobile phone in release/debug mode.
using latest packages.
xamarin.forms:4.8.0.1560

@XamarinInfo
Copy link

Hi Bros,

It's working fine for me.
I just downgraded Xamarin.Build.download to 0.8.0.

Restarted Visual studio.

@alaskanrogue
Copy link

alaskanrogue commented Oct 26, 2020

I see the error message, but haven't been impacted yet that I know of. Is there any documentation as to how to migrate?

@chrisjmartinez
Copy link

I was able to workaround this issue by removing some duplicate Xamarin.Firebase references and changing Linker options to "Link SDK assemblies only". The XDB100 warning is a bit of a red herring here so hopefully Microsoft will resolve this soon.

@Redth
Copy link
Member

Redth commented Oct 26, 2020

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

@jbtdevgit
Copy link

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?

@mfeingol
Copy link
Author

mfeingol commented Jan 8, 2021

@Redth: a gentle ping on this question.

@Redth
Copy link
Member

Redth commented Jan 9, 2021

@moljac ^ ?

I think there's probably already an update with these changes...

@alaskanrogue
Copy link

As of the current VS 2019 Pre - Preview 2.0 release, the problem is still present.

@mfeingol
Copy link
Author

cc @moljac

@thisisthekap
Copy link

We keep seeing this exception randomly on Xamarin.Android CI Builds using Microsoft Hosted build agents.

@jvom
Copy link

jvom commented Jan 31, 2021

+1

@tinonetic
Copy link

tinonetic commented Feb 14, 2021

Keep seeing this. Visual Studio 2019, Update 16.10.0

2021-05-31

@josephntiotangco
Copy link

+1

@valentasm1
Copy link

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

@Chocopro713
Copy link

+1

@xmine64
Copy link

xmine64 commented Apr 29, 2021

I have same problem.
I got it today. I get the error on both debug and release profiles, debug version works but release version doesn't start.
I decompiled output file, and I noticed that debug build has androidx.multidex.MultiDexApplication in it, but release build doesn't.

@gireeshkottayam
Copy link

same problem @ vs2022 !
Untitled

@GeorgesGITHUB
Copy link

I just downgraded Xamarin.Build.download to 0.8.0.

how?

@nmpasdanis
Copy link

nmpasdanis commented Nov 29, 2022

anyone that solved this issue??
I Have the same issue and i do not know what to do

@thisisthekap
Copy link

@mpasdan I explicitly installed Xamarin.Build.Download 0.11.0 to the native projects.

@moljac
Copy link
Member

moljac commented Nov 29, 2022

@nmpasdanis
Copy link

okey thank you I 'll try

@nmpasdanis
Copy link

i could not solve the issue, i installed the package in the native projects but didn't change anything, yet there is the warning.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests