Bug 27760 - Android application is giving build error.
Summary: Android application is giving build error.
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Windows
: Highest blocker
Target Milestone: 6.0 (C6)
Assignee: dean.ellis
Depends on:
Reported: 2015-03-09 02:39 UTC by Jatin
Modified: 2015-07-22 15:04 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Comment 1 PJ 2015-03-09 14:55:16 UTC
Hi Jatin, this build is from master and not from XA 5.1, moving off milestone.
Comment 2 dean.ellis 2015-07-13 11:10:24 UTC
Hi Jatin

I'll take a look at this. In the mean time can you post the Diagnostic output place. It looks like the build logs have a "Normal" verbosity it would be preferable to have the "Diagnostic" output.
Comment 3 dean.ellis 2015-07-13 11:52:32 UTC

I am unable to replicate this on but 5.1.230 (https://wrench.internalx.com/Wrench/ViewLane.aspx?lane_id=495&host_id=63&revision_id=579387) 

The android application builds, deploys and debugs without any issues. 

Can you provide the diagnostic output for your errors please,
Comment 4 Peter Collins 2015-07-22 15:04:33 UTC
Chances are good that this popped up during a rather broken period of master smoke testing. I am unable to reproduce the failure, and it has most likely since been resolved.

@Jatin please reopen if you can still reproduce this using a recent XVS master build.