Bug 22672 - Building Xamarin.iOS project fails
Summary: Building Xamarin.iOS project fails
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-09-05 00:58 UTC by sothy.chan
Modified: 2014-09-10 10:51 UTC (History)
4 users (show)

Tags:
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 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:
Status:
RESOLVED NOT_REPRODUCIBLE

Description sothy.chan 2014-09-05 00:58:09 UTC
1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(319,3): error : Unexpected error - Please file a bug report at http://bugzilla.xamarin.com

That's what it says.  Please let me know how to move forward.
Comment 1 sothy.chan 2014-09-05 01:07:15 UTC
Cleaned and rebuilt.  Error disappeared, but thought I reported it anyways since it told me to.
Comment 2 Danish Akhtar 2014-09-10 09:46:26 UTC
Could you please provide us the Xamarin build info and attached your project, so we can try to reproduce this issue at our end.

Thanks
Comment 3 PJ 2014-09-10 10:51:10 UTC
I think Sothy already responded and said he resolved the issue with a rebuild. I'm going to RESOLVE this one as WORKSFORME, but Sothy please feel free to REOPEN if you experience the issue again.