Bug 3160 - Fails at end of build and won't complete build seen it in the past strange error
Summary: Fails at end of build and won't complete build seen it in the past strange error
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-01-31 11:10 UTC by kenny goers
Modified: 2013-12-05 18:36 UTC (History)
3 users (show)

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

CSPROJ file (12.74 KB, application/octet-stream)
2012-01-31 13:40 UTC, kenny goers

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:

Description kenny goers 2012-01-31 11:10:11 UTC
At the end of the build of the final .APP

Build complete -- 0 errors, 12 warnings

Building: Ecolab.SalesPad.Touch.ITR (Debug|iPhoneSimulator)

---------------------- Done ----------------------

Build successful.
Build failed. '/Users/mac/Projects/ecolab-salespad/Ecolab.SalesPad.Touch/bin/iPhoneSimulator/Debug/Settings' is not a working copy

Where the "Settings" is a directory with sub directories that contain content. What does "is not a working copy" even mean?
Comment 1 Sebastien Pouliot 2012-01-31 11:23:48 UTC
This looks like an MD issue. Can you provide the MonoDevelop version number you're presently using ?
Comment 2 Alan McGovern 2012-01-31 12:30:43 UTC
This is an issue which has cropped up recently involving MonoDevelops support for different VersionControl systems. So far it has only manifested with SVN support.

Would you be able to attach a copy of your csproj file. When attaching a document you can click the button to make it private, for xamarin employees only, if it contains confidential information. A fix for a very similar issue has already been committed but this could be another manifestation of the problem, which is why having the csproj would help diagnose this further.
Comment 3 kenny goers 2012-01-31 13:40:35 UTC
Created attachment 1294 [details]
Comment 4 Steve Williams 2012-02-14 08:35:27 UTC
I have just come across this issue as well.  Some of the projects in my sln are in a SVN working copy.  I have found that hitting Build again will get a few files further.  Each subsequent attempt to build will get a few files further through the output folder containing content.

Mono for Android not installed
Monotouch: 5.2.3
Comment 5 Alan McGovern 2012-02-15 05:43:08 UTC
This bug should be fixed with commit 01b7153ad in git master. We are planning on releasing this in the next week or two with a version number of MonoDevelop 2.8.8.

If you'd like to try a completely untested build straight from our build servers which contains the fix for this bug, you can download https://files.xamarin.com/~alan/MonoDevelop-svn_fix.dmg . If the issue is not gone with this, could you provide the stacktrace that should be displayed in the Exception dialog in monodevelop and also the contents of the MonoDevelop.log file from ~/Library/Logs/MonoDevelop-2.8/MonoDevelop.log.
Comment 6 PJ 2013-11-19 17:05:40 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 7 PJ 2013-12-05 18:36:07 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.