Bug 3076 - Xcode permission exception when opening xib from MonoDevelop
Summary: Xcode permission exception when opening xib from MonoDevelop
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8 beta 3
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-01-25 18:10 UTC by jesse.attas
Modified: 2013-12-05 18:36 UTC (History)
2 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:

Description jesse.attas 2012-01-25 18:10:51 UTC
Since the upgrade was pushed to me today, I haven't been able to open any XIB files from my MonoDevelop solution. The text of the error dialog I get is copied below.

If I look for the directory in the error message, the obj directory exists but the Xcode one doesn't. The obj directory has permissions drwxr-xr-x. Adding write permission doesn't help.

This has been reproduced on 2 different machines with We've tried doing a clean build, deleting the obj directory, and rebooting MonoDevelop but none of them helped.

An error has occurred

Error updating Xcode project. Access to the path "/******/obj/Xcode/0/SecondViewController.xib" is denied.

System.UnauthorizedAccessException: Access to the path "******/obj/Xcode/0/SecondViewController.xib" is denied.
  at System.IO.File.SetLastWriteTime (System.String path, DateTime lastWriteTime) [0x00031] in /private/tmp/monobuild/build/BUILD/mono-2.10.8/mcs/class/corlib/System.IO/File.cs:468 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeSyncedContent.SyncOut (MonoDevelop.MacDev.XcodeSyncing.XcodeSyncContext context) [0x0007c] in /Users/builder/data/lanes/monodevelop-mac- 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeMonitor.UpdateProject (IProgressMonitor monitor, System.Collections.Generic.List`1 allItems, MonoDevelop.MacDev.XcodeIntegration.XcodeProject emptyProject) [0x00324] in /Users/builder/data/lanes/monodevelop-mac- 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeProjectTracker.UpdateXcodeProject (IProgressMonitor monitor) [0x00000] in /Users/builder/data/lanes/monodevelop-mac-
Comment 1 Mikayla Hutchinson [MSFT] 2012-01-25 18:17:53 UTC
Is the project on a network/nonstandard filesystem? Is it under Perforce version control?
Comment 2 jesse.attas 2012-01-25 18:20:36 UTC
It's on the local disk but under TFS. The directory listed in the error message is not under source control though.
Comment 3 jesse.attas 2012-02-02 14:55:19 UTC
I upgraded to MonoDevelop today and the issue went away for me. I don't know if it was a fix you put in or a side effect of the installation, but I'm happy for now!
Comment 4 PJ 2013-11-19 17:05:48 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 5 PJ 2013-12-05 18:36:16 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.