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.
Adding a control directly to the XML source in the .axml file, the newly added control is not picked up by the build system and the deployed app does not show the new control.
## Steps to reproduce
1. Open Visual Studio and create a new Android project.
2. Build and deploy to a simulator.
3. Open the Main.axml file in Android Designer and switch to the Source tab.
4. Add a new Button directly in the XML.
5. Build and deploy the app.
Expected result: The newly added button will be in the displayed UI on the device/ simulator.
Actual result: Only the original button is displayed.
## Regression status
This seems to be a regression:
BAD: XVS 18.104.22.168
If you add the control in the GUI designer, the new control is picked up by the build system and the control is shown when you deploy the app.
Other edits in the source XML do get picked up, IOW if I edit the text property for a control, the edit is reflected on build and deploy. So this issue seems to be only when a new control is added in the XML source.
If you do edit something in the GUI editor after adding the control to the XML source, then the new control is picked up by the build system and will be displayed in the UI on device simulator.
Microsoft Visual Studio Professional 2015
Version 14.0.23107.0 D14REL
Microsoft .NET Framework
Installed Version: Professional
Visual Basic 2015 00322-40000-00000-AA850
Microsoft Visual Basic 2015
Visual C# 2015 00322-40000-00000-AA850
Microsoft Visual C# 2015
Visual C++ 2015 00322-40000-00000-AA850
Microsoft Visual C++ 2015
Visual F# 2015 RC 00322-40000-00000-AA850
Microsoft Visual F# 2015 RC
Windows Phone SDK 8.0 - ENU 00322-40000-00000-AA850
Windows Phone SDK 8.0 - ENU
Application Insights Tools for Visual Studio Package 1.0
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 14.0.20626.0
ASP.NET and Web Tools
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
For additional information, visit http://www.asp.net/
Common Azure Tools 1.5
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Generates unit test code for methods in classes under test.
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
NuGet Package Manager 3.2.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 14.0.50616.0
Microsoft SQL Server Data Tools
Visual Studio Tools for Universal Windows Apps 14.0.23309.00 d14oob
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.
Xamarin 22.214.171.124 (f869dba)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 126.96.36.199 (46c3f7e)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 188.8.131.52 (49ba15e)
Visual Studio extension to enable development for Xamarin.iOS.
@Juan (in private comment above asking if I can confirm if issue persists in latest version of Cycle 7 builds)
Yes, I have confirmed that this issue is resolved using the latest Cycle 7 builds in the Alpha and Beta channel.
As per Comment 3, marking the bug as resolved. Thanks!