Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
# Steps to reproduce
1. File -> New -> Cross-Platform -> Cross-Platform App -> Blank Forms App.
2. Open MainPage.xaml.
3. Try to type and get XAML IntelliSense.
# Expected behavior
XAML IntelliSense functions properly for Android target.
# Actual behavior
XAML IntelliSense functions properly only for iOS target, as seen here:
# Supplemental info (logs, images, videos)
# Test environment (full version information)
Environment Info: https://gist.github.com/pierceboggan/5b5fba9ff76ed6f5841a0136303b9d4a
Created attachment 22782 [details]
I could reproduce the issue. However after building the Android project and reopening the solution, the xaml intellisense started to work with any target selected. So probably the cause of the issue is some lack of metadata at the time of opening the solution. Since there are a couple of workarounds (selecting iOS or building Android and reoponing the solution) I would postpone this issue for 15.4, decrease importance from blocker to normal and also ping XAML lang service guys to take a look at it. Please let me know if you think we should tackle before 15.4
*** This bug has been marked as a duplicate of bug 56629 ***
Oops, wrong bug!
This issue is affecting the critical path of most of our users: File -> New -> Forms app. Even though there is a workaround, IntelliSense is a high visibility issue as developers expect it to just "work" out of the box. Issues affecting IntelliSense also affect first run, as there is no way for users to discover XAML controls from within the IDE (as there is no toolbox for XAML controls).
I just experienced this as well. However after building the solution and closing and re-opnening visual studio, although selecting Xamarin.Android as the target worked for Intellisense, selecting the UWP target did not. With the UWP target selected, I only got intellisense for UWP types, not Xamarin.Forms types.
*** Bug 45848 has been marked as a duplicate of this bug. ***
*** Bug 35075 has been marked as a duplicate of this bug. ***
*** Bug 34023 has been marked as a duplicate of this bug. ***
This issue is related to designTimeBuild, in this mode XA skip task `GetAdditionalResourcesFromAssemblies` and the cache required for `Aapt` task is not saved.
Moving the bug to Android for visibility from the right team.
*** Bug 57275 has been marked as a duplicate of this bug. ***
*** Bug 52908 has been marked as a duplicate of this bug. ***
Can we retest this on d15-4?
This might be fixed by: https://github.com/xamarin/xamarin-android/pull/668
PR 688 did not fix the problem :/
We have a bit of a dilemma it seems. The warnings in the intelligence build come from the fact that the additional resources have not been downloaded. But we don't want to download them because they can take ages to get. So to fix them we need to download the resources. But we can't download the resources because it will probably lock up the IDE while it downloads.
I'll investigate to see if there is a work around we can do
Also worth noting in my debugging with @Alan that this is only happening with Shared Projects, not library projects.
The reason it does not work for Shared projects is because they are built as part of the android app.. and its the android app that needs all the support libraries in place to build property. Currently that is not done for designative builds because of the problems with getting stuff from the internet (which might take a while and lock the IDE)
I am in the process of Reworking GetAdditionalResourcesFromAssemblies.
The idea being that in a DesignTimeBuild we can do everything BUT download zips..
So if the required resource files are in the android-idk/extras directory they will be extracted. However if the Task needs to hit the internet , it won't...(for desigtime) locking up the IDE for 10 minutes while it downloads something in a designative build is a HUGE problem, and will make things look allot worse for the user.
Hopefully this will be fixed by xamarin-android/master/1cd582ec
This fix will only work IF the m2repository files are installed in android-sdk/extras. If they are not and the system needs to download the files, this bug will persist.
There is nothing I can do about that until we start packaging the resources in the Nuget packages.
Created attachment 24164 [details]