Re: New documentation update resolves "921" problem
Re: New documentation update resolves "921" problem
- Subject: Re: New documentation update resolves "921" problem
- From: Ronald Hayden <email@hidden>
- Date: Tue, 17 Jun 2008 14:38:52 -0700
Is there a way to force Xcode to do an update even if it thinks one
is not needed?
To force an update to a doc set, you need to delete the doc set from
the file system so Xcode will re-download it. You can do this by
control-clicking the doc set in the doc window TOC, selecting "Reveal
in Finder", then deleting it.
-- Ron
On Jun 17, 2008, at 2:11 PM, Daniel Hazelbaker wrote:
On Jun 17, 2008, at 1:26 PM, Ronald Hayden wrote:
Thanks for letting us know. I have giving up yesterday night and
uninstalled/reinstalled Xcode to get docs working again.
To cause Xcode to check for a doc release before it otherwise
would, use the gear menu in the lower left of the doc window and
choose Documentation Set Updates->Update All Documentation Sets Now.
I also recommend setting the default frequency (on that same menu)
to Daily, which is now the default for new installations.
Is there a way to force Xcode to do an update even if it thinks one
is not needed? To be fair I am not sure I need to as it seems to be
working and shows the right version, but that latest update took
forever to run on my desktop (MBP was quick and easy). I let it run
for 4 hours (CPU cranking the whole time) and finally force-quitted
it while it was still saying "installing update" (or some such
thing). I would feel better if I could just wipe it away and force
it to download again.
Daniel
P.S., I think the problem was due to the fact I clicked the update
icon for all 3 of my doc sets at the same time, when I ran the other
2 one at a time it worked fine. If you know how I can make Xcode
forget about those I will try to replicate.
-- Ron
On Jun 17, 2008, at 12:21 PM, Markus Spoettl wrote:
On Jun 17, 2008, at 3:53 AM, Bill Cheeseman wrote:
I automatically received new documentation updates from Apple
early this
morning. They appear to have resolved the "921" problem created
by the
update a couple of days ago.
On one machine, I had to quit Xcode and relaunch it before the
fix took
effect; on the other machine, I did not. I had been working for a
couple of
hours on a project on the machine where quit-and-relaunch were
required.
Thanks for letting us know. I have giving up yesterday night and
uninstalled/reinstalled Xcode to get docs working again. We might
still be waiting if I hadn't done that :)
Regards
Markus
--
__________________________________________
Markus Spoettl
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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