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 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.
Description of Problem:
I am getting so many errors mainly deployment errors when I try to Debug my Second Android Application in Xamarin for Visual Studio v22.214.171.1247. These bugs are mainly found after Publishing the first Android App project. After Publishing an Android Application using Xamarin Visual Studio, I won't be able to Debug a Second Project. When I try to Debug a second Project I will get a lot of Errors(The Errors are mentioned below in "Actual Results:").
Also, even when I try to Debug my First Project again after trying to Debug my Second Project, it won't work. Showing the same type of errors.
Also, .axml Layout file is not compiling properly on the second project. After giving a name to a new or an existing Visual Element such as a Button (Ex: @+id/EqualsButton) in the Layout file, the intellisense won't recognise any New Visual Elements. And even when I try to Build the solution, an error pops up saying that "EqualButton" doesnot exist!"
Also, the drawable Icons won't Compile Properly. Showing the same type of error as in case of Layout.
These problems were also found in the earlier versions of Xamarin for Visual Studio. But being a Newbie I couldn't understand those errors. Please fix these problems. Thanks in Advance!
Solution that I found:
The only solution that I found to fix this problem is that I need to perform a Full-Uninstall of Visual Studio & Xamarin Studio & then do a Full-Reinstall of both after Rebooting my PC, which consumes hours of time.
Steps to reproduce the problem:
1. Create a New Android Project in Visual Studio 2015 then do some coding
2. Populate the .axml file with Visual Elements (such as Buttons, EditText, etc..)
3. Bind those with the code, also give some names to the Visual Elements (Ex: @+id/NewButton)
4. Debug the Application to make sure works correctly & Publish the Application.
5. Then close Visual Studio & Reboot the PC.
6. Then open Visual Studio Again & create another New Android Project
7. This time write a different code & populate the Layout file with Visual Elements & try to Bind those in the code & then build & Debug it.
The Error happened to me at this time. I won't be able to use the Layout resource. Neither the Intellisense pops up with the required visual Elements. Only the Element "MyButton" (default element name) is present. I also Cleaned the solution & Rebuilded it again, but Fails.
1. "aapt" exited with code 1
2. The file "obj\Debug\android\bin\packaged_resources" does not exist.
3. "EqualButton" doesnot exist!"
No such error messages!
How often does this happen?
This happens when I try to Debug my Second Project after the Release or Debug of my First Project in Xamarin Visual Studio.
I'm sorry you're having problems using the product :(
Could you provide the two sample repro solutions that trigger the error for you?
We also need the build logs (either from VS or from command line builds via msbuild), ideally in Detailed verbosity, as well as VS version information from Help > About Visual Studio.
Thanks in advance!
As we've added several improvements to our build system and deploying/debugging mechanism since the bug was reported, I'm resolving it tentatively as Fixed.
That said, if you're still facing this issue with current bits, please feel free to reopen the bug.