Bug 29987 - "Unknown MSBuild failure" when building monotouch-samples project SpriteTour
Summary: "Unknown MSBuild failure" when building monotouch-samples project SpriteTour
Alias: None
Product: Tools
Classification: Mono
Component: msbuild (show other bugs)
Version: 4.0.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Ankit Jain
Depends on:
Reported: 2015-05-12 15:08 UTC by Dylan Kelly
Modified: 2018-01-10 11:46 UTC (History)
7 users (show)

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

SpriteTour sample (1.17 MB, application/zip)
2015-05-12 15:08 UTC, Dylan Kelly
IDE log (21.97 KB, text/plain)
2016-11-17 07:09 UTC, Andres G. Aragoneses

Description Dylan Kelly 2015-05-12 15:08:35 UTC
Created attachment 11174 [details]
SpriteTour sample

On master (XI I am unable to successfully build the monotouch-samples project SpriteTour (https://github.com/xamarin/monotouch-samples/tree/master/SpriteTour), however on stable (XI I am able to successfully build. The error thrown does not give any indication as to what the issue may be.

Steps to reproduce:
1) Open attached project
2) Clean project
3) Build project for any configuration

Expected Result:
Project successfully builds

Actual Result:
Build fails, throwing the error: ".../SpriteTour.csproj(1,1): Error: Unknown MSBuild failure. Please try building the project again (SpriteTour)"

Environment info:

=== Xamarin Studio ===

Version 5.9 (build 431)
Installation UUID: 476d6850-22f1-4443-980f-6137a73b4b1f
	Mono 4.0.0 ((detached/d136b79)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400000143

=== Apple Developer Tools ===

Xcode 6.3.1 (7703)
Build 6D1002

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: f0052cc
Branch: master
Build date: 2015-05-12 10:48:47-0400

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/dylankelly/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.3   (API level 18)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 509000431
Git revision: 7560726734fc7267de2fa9abed2509968deefaa8
Build date: 2015-04-17 19:25:48-04
Xamarin addins: 2e772c734ab3148054eae7bf8949f340fdeb5e5e

=== Operating System ===

Mac OS X 10.10.3
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-05-13 13:53:28 UTC
This looks like a bug in our MSBuild implementation.

This is what shows up in a command-line build with xbuild: https://gist.github.com/rolfbjarne/dc2b10d91424204d283c
Comment 2 Dylan Kelly 2015-05-13 17:34:52 UTC
If it helps, the prebuilt sample "FieldService" (https://github.com/xamarin/prebuilt-apps/tree/master/FieldService) and the monotouch-sample Tabbed_Images (https://github.com/xamarin/monotouch-samples/tree/master/Tabbed_Images) are experiencing the same ArgumentNullException on master.
Comment 3 Oleg Demchenko 2015-05-14 21:09:49 UTC
Experiencing the same issue with FieldService and XI Put this bug to CONFIRMED
Comment 4 Andres G. Aragoneses 2016-11-17 07:05:58 UTC
I'm getting "Error: Unknown MSBuild failure. Please try building the project again" when trying to build the stock F# Xamarin.Forms solution that Xamarin Studio 6.1.2 (build 44) [stable channel] creates by default for Android (on Windows).

So you should remove the "monotouch" bit from the subject because the problem seems to be not so specific.

This is also being reported many times in the forum: https://forums.xamarin.com/discussion/31194/unknown-msbuild-failure-please-try-building-the-project-again-on-migrating-classic-apis-to-unified
Comment 5 Andres G. Aragoneses 2016-11-17 07:09:35 UTC
Created attachment 18497 [details]
IDE log

Attaching my log file.

Note You need to log in before you can comment on or make changes to this bug.