• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 3.0 file trashing situation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 3.0 file trashing situation


  • Subject: Re: Xcode 3.0 file trashing situation
  • From: Chris Espinosa <email@hidden>
  • Date: Wed, 30 Jan 2008 09:24:59 -0800


On Jan 30, 2008, at 4:32 AM, Knowledge Engineering wrote:

I have filed a bug report as follows and think users of this list might be interested.
This bug has bitten twice on two different systems. The first time I thought it was a fluke.


I like to create non-compile files (.txt, .m, whatever) to collect notes, hold cut code, etc.
These are not in any target (important criterion).
Bug is that Xcode somehow moves or creates them in the Trash, where they can be lost forever if Trash is emptied.


Steps to Reproduce:
1. In an XCode project, "New File..." File type does not seem to matter.
2. Uncheck the "In Target" checkbox .
3. Continuing using XCode, editing files.
4. At some point, you will get the "File has gone missing" error alert from XCode. The file title will go red in sidebar.
5. YOU MAY NOT KNOW IT, BUT at this point file is actually in Trash. It can be recovered manually before Trash is emptied. Otherwise, it's gone.

Thanks for the bug report, it's the first one we've received on such a syndrome.


Some follow-up questions:

• This is New File in Project, right? The file is added to the project but no targets? (It's important to know the difference between New Empty File and New File in Project. Its target membership should not matter at all, and the other response that you should add it to a useless target is inaccurate).

• Do you enter any text into the file?

• Do you ever save the file?

• Do you Build the project, and if so, do you have Save before Building checked?

• Are you using SCM, Snapshots, or any other Xcode feature that deals with saving or reloading files?

• Where are you creating the file?

The only code path that calls the new Leopard API to move a file to the Trash is taken when you explicitly delete a file with the Delete command (or implicitly via SCM). Obviously, something external to Xcode could be moving the file to the Trash behind its back, or there could be accidental invocation of the Delete path that we don't know about. It would be helpful to know just what you're doing around the "at some point" that the file goes missing.

Chris _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Xcode 3.0 file trashing situation
      • From: William Bates <email@hidden>
References: 
 >Xcode 3.0 file trashing situation (From: Knowledge Engineering <email@hidden>)

  • Prev by Date: Re: Link problem
  • Next by Date: Re: eof() for file descriptors missing?
  • Previous by thread: Re: Xcode 3.0 file trashing situation
  • Next by thread: Re: Xcode 3.0 file trashing situation
  • Index(es):
    • Date
    • Thread