References to Xamarin.Android.Support.XXX and System.ObjectModel in Xamarin.Android (Xamarin.Forms) are lost periodically (path empty) about xamarinalliance

[JonDouglas]

I believe that this might be related to a old version of Xamarin.Build.Download. Can you please ensure that you update it to the latest prerelease package?

https://www.nuget.org/packages/Xamarin.Build.Download/0.4.3-beta3

[JonDouglas]

There should be a new stable release that resolves the intellisense issues:

https://www.nuget.org/packages/Xamarin.Build.Download/

As for the warnings here, I believe our components team is looking into why certain warnings like unknown enum context Scope.LIBRARY_GROUP are appearing. I believe you can try using the 25.2.0-beta1 Support Library packages in hopes of this making it already. However there should be a new release soon that addresses the similar warnings.

[lilepeeps]

Thanks for the question. We'll come back to you.

[Trubador]

I have just installed latest version per your suggestion and then restarted Visual Studio.
Unfortunately this yields the same result.
Could it be that my installation is corrupt?
I have had VS installer repair a couple times now in addition to what I have done as stated in the post.

[Trubador]

I have updated Xamarin.Forms and any other Xamarin Nuget packages in my Solutions to latest prerelease version, to no avail unfortunately. Same errors.

What can I do to alleviate the problem?
Reinstall my pc and Visual Studio to solve the problem or will it be recurring ?

[Trubador]

Where can I go to get support for this fundamental issue ? :(

[Trubador]

Hi there. I have tried to correct the problem by installing the beta version of xamarin as suggested, however it has not had any effect. I am still not sure if the installation is corrupt or that there is some serious issues with xamarin tools that causing the issue. As for now I have switched to native android development, until this issue is corrected. Do let me know if you figure out something new in regards to this issue. I have not yet tested with a new stable version of xamarin.