tags:

views:

1136

answers:

5

When I'm searching for something in the Developer Documentation of Xcode, I constantly get "File not Found"/"The requested file was not found in any documentation set."

The odd thing is, it still works. E.g., if I search for NSSound, I can find NSSound.

The error dialogue is invoked whenever it attempts to search as I type, which makes it particularly annoying.

This only happens when I select certain documentation sets (e.g., "iPhone OS 3.1 Library"). I tried deleting it & re-installing, but the same result. (Perhaps I didn't remove everything?)

A: 

That was your early Thanksgiving treat from Apple. They sent a docset 3.1 "update" out about 4-5 days ago and F'ed up alot of peoples documentation. It's basically unusable for me right now...I can't do anything without having do dismiss a never-ending barage of "page not found" error dialogs. It also trashed 50% of the favorites links I had on the left panel of documents. I assume these were from the docsets it now want's me to re-subscribe to but gives an error every time I try.

Haven't seen alot of posts about it yet so I would bet that Apple will likely do nothing. If it were possible to get a human on the phone over there I would have some answers to go along with the frustration.

Happy Thanksgiving

PS. Best to turn OFF the auto-update option in documentation. If not for having that option ON I'd currently be oblivious to this issue and capable of viewing my documentation.

Redrocks
A: 

I am getting this as well. I am guessing it is not affecting very many people though, since searching "the requested file was not found in any documentation set" in google is still only turning up four hits. And it is affecting my desktop but not my laptop.

Have either of you tried reinstalling Xcode?

Pmatt
I did, to no avail.
Bill
+3  A: 

I put up a post to fix this over here: http://allens-techlog.blogspot.com/2009/11/fixing-xcode-requested-file-was-not.html

Allen
A: 

I got this issue after install the latest SDK 3.1.2. I try reinstall xcode, but the error still pops up!

Hary
+1  A: 

Another fix is to change your searching from "All Doc Sets" to "Apple iPhone OS 3.1". Once you've done that, select the "Apple iPhone OS 3.0" docset. Although it's old you won't get the error and in a month or two you can change it back.

dnevins