Stuck on DP1 (14A283x instead of 14A283o) (merged)

[Jaypi]

Hi,
I just installed Yosemite DP1, but there are no further updates.

I'm still running 14A238x although the AppStore tells me that there are no updates.

Had anybody else that problem and how can I fix it?

 

[simsaladimbamba]

Do you have a developer account?

 

[iBlazed]

Do you have a developer account?

Even if you don't, the updates still usually get pushed to any Mac detected running an outdated DP.

 

[helix21]

Stuck on DP1 (14A283x instead of 14A283o)

Hi guys,

I've got a feeling I'm still stuck on DP1. I've only had two "Developer Preview Updates" that were over a gig in size applied. They didn't explicitly say "Develop Preview 2/3".

Now I don't have Dark Mode or any of the changes notes in DP3.

About my Mac reports a version of 14A283x ; whereas DP3 is 14A283o I believe.

No matter how many times I refresh software update, I don't get an update.

Anyone else have similar trouble or know how to fix this?

 

[Hiiambo]

Log into the developer portal and download the Delta for DP3.

 

[mmomega]

Log into the developer portal and download the Delta for DP3.

I had to do this for my Mac Mini. The other machines I'm testing on update just fine from the MAS except for the Mini.

I had to get the delta for DP2 and DP3, both would restart to install the update and then hang with 17 minutes remaining and never complete the install.

 

[Jaypi]

Yes - I just installed manually a delta update now. It works finally

 

[Brian Y]

run

sudo softwareupdate -i -a

For some reason the app store software update recognises a failed 10.10 update 1 install as being installed and won't offer it again .

 

[Brian Y]

Just posted this in another thread, but

sudo softwareupdate -i -a

will normally do the trick.

 

[Nwashko]

Updating Past DP1 Help?

Hi guys, new to the forum and I apologize if this has been answered before, but I can't find anything anywhere. I've been trying to update past DP1 since the second beta came out, and I have been unable to. When I go into the App Store, it shows the option to update, but when I click, it prompts me to restart, just like any other update. I click it, and then it does nothing but show the screenshot I'm including below. No restart, no download, nothing. Can anyone help? I'm running a mid-2012 13" MBP.

 

[Nwashko]

I tried that as well, and it won't even let me install the .pkg file.

 

[mende1]

Redownload the Developer Preview installer. If the problem still appears, format the OS X Yosemite partition and reinstall OS X Yosemite

 

[Nwashko]

I got it working! This can be deleted/closed now. Thank you mende1!

 

[bbfc]

Hi guys,

I've got a feeling I'm still stuck on DP1. I've only had two "Developer Preview Updates" that were over a gig in size applied. They didn't explicitly say "Develop Preview 2/3".

Now I don't have Dark Mode or any of the changes notes in DP3.

About my Mac reports a version of 14A283x ; whereas DP3 is 14A283o I believe.

No matter how many times I refresh software update, I don't get an update.

Anyone else have similar trouble or know how to fix this?

Those developer preview updates were DP2 and DP3.

DP2 was released as OS X 10.10 Update 1, and DP 3 was Developer Preview 3 1.0.

 

[grahamperrin]

From 14A238x to 14A261i to 14A283o

...
sudo softwareupdate -i -a
...

For this problem, try a more specific command as part of a structured routine.

01) start 14A238x

02) ignore App Store

03) unmount all volumes except the 14A238x volume from which you started

04) in Terminal,

sudo softwareupdate -v -d "OS X 10.10 Update-1.0" ; open /Library/Updates

05) after Terminal opens the window in Finder, browse to the update .pkg

06) tag then open the .pkg and follow the routine that's given in Installer.app

07) when Installer prompts you to restart, do so

08) if it becomes necessary to force a restart, then reuse the .pkg that you tagged at step (06)

09) with 14A261i running, proceed in a similar way ...

10) ignore App Store

11) unmount all volumes except the 14A261i volume from which you started

12) in Terminal,

sudo softwareupdate -v -d "OS X 10.10 Update-1.0" ; open /Library/Updates

13) after Terminal opens the window in Finder, browse to the non-tagged update .pkg

14) to the non-tagged update .pkg, apply a unique tag

15) open the .pkg and follow the routine that's given in Installer.app

16) when Installer prompts you to restart, do so

17) if it becomes necessary to force a restart, then reuse the .pkg that you tagged at step (14)

 

[tywebb13]

There is an easier way than that.

In the apple developer forums there are direct links to the DP2 and DP3 installers which you can download with a browser instead of the mac app store.

Most developers who have had problems with the mac app store who tried it this way instead have said that this was more successful.

Of course I assume you are a developer and have access to apple's developer forums.

I also note that putting the links here on macrumors is against macrumors rules and so previous postings here which did that have been deleted by moderators, and will continue to be if such attempts are made again, so there is no point in doing so. Just go to apple's developer forums and get them from there instead if you need to.

 

[grahamperrin]

Understanding the problem

There is an easier way …

Close observation of the routine above, by someone with an eye for detail, may help to understand a root cause of the problem.

I assume you are a developer …

I use Feedback Assistant, and Apple has received my observations.

 

[Brian Y]

For this problem, try a more specific command as part of a structured routine.

01) start 14A238x

02) ignore App Store

03) unmount all volumes except the 14A238x volume from which you started

04) in Terminal,

sudo softwareupdate -v -d "OS X 10.10 Update-1.0" ; open /Library/Updates

05) after Terminal opens the window in Finder, browse to the update .pkg

06) tag then open the .pkg and follow the routine that's given in Installer.app

07) when Installer prompts you to restart, do so

08) if it becomes necessary to force a restart, then reuse the .pkg that you tagged at step (06)

09) with 14A261i running, proceed in a similar way ...

10) ignore App Store

11) unmount all volumes except the 14A261i volume from which you started

12) in Terminal,

sudo softwareupdate -v -d "OS X 10.10 Update-1.0" ; open /Library/Updates

13) after Terminal opens the window in Finder, browse to the non-tagged update .pkg

14) to the non-tagged update .pkg, apply a unique tag

15) open the .pkg and follow the routine that's given in Installer.app

16) when Installer prompts you to restart, do so

17) if it becomes necessary to force a restart, then reuse the .pkg that you tagged at step (14)

There's no reason to do this. All you're doing is downloading one specific update, and manually installing it. It just means you have to faff around rather than running one command.

And you won't learn anything from running softwareupdate verbosely. softwareupdate won't fail - it's the app store that has trouble applying the update. All you're doing is making more work for yourself.

 

[grahamperrin]

There's no reason to do this. All you're doing is downloading one specific update …

No, there's more.

 

[Brian Y]

No, there's more.

There really isn't.

You tell software update to download "-d" the update. The second part of the command just opens a finder window.

You then install the update manually (you could have just done this with /usr/sbin/installer).

You then repeat the process. This is no different to using -a -i, then restarting, then using -a -i again - other than, using your method, you have to navigate through finder, manually tag things (why?) and THEN install further updates afterwards. In fact, you don't need to use softwareupdate the second time - the app store will be fine - it's ONLY the first update that fails to install, not DP3.

It's pointless. It's just more work for no reward.

 

[grahamperrin]

… You then repeat the process. This is no different …

There's a difference.

Close observation of the routine above, by someone with an eye for detail, may help to understand a root cause of the problem. Observe not only what's written above; observe closely what occurs when the routine is followed. We need not (should not) share the results in public, but differences may be remarkable.

It's pointless. It's just more work for no reward.

First and foremost, consider the nature of feedback to Apple.

You could do as little work as possible; you could rush to the simplest or speediest workaround, without attempting to more deeply understand the cause(s) of a problem.

Alternatively, you could take time work through things in a more systematic way and in doing so, increase the likelihood of feedback that will help Apple to improve its software. At the same time you may gain – for yourself – a deeper understanding of an area.

There are multiple points of view; multiple possible rewards. No single way to approach a problem such as this.

----

All that said: attention to just one of my suggested steps may raise an eyebrow with someone who's familiar with softwareupdate routines. Mac OS X Power Tools (2006) will be outdated in many ways, but there's a point of interest on page 453.

 

[Brian Y]

There's a difference.

Close observation of the routine above, by someone with an eye for detail, may help to understand a root cause of the problem. Observe not only what's written above; observe closely what occurs when the routine is followed. We need not (should not) share the results in public, but differences may be remarkable.



First and foremost, consider the nature of feedback to Apple.

You could do as little work as possible; you could rush to the simplest or speediest workaround, without attempting to more deeply understand the cause(s) of a problem.

Alternatively, you could take time work through things in a more systematic way and in doing so, increase the likelihood of feedback that will help Apple to improve its software. At the same time you may gain – for yourself – a deeper understanding of an area.

There are multiple points of view; multiple possible rewards. No single way to approach a problem such as this.

----

All that said: attention to just one of my suggested steps may raise an eyebrow with someone who's familiar with softwareupdate routines. Mac OS X Power Tools (2006) will be outdated in many ways, but there's a point of interest on page 453.

As I said before - this process will not reveal anything about the problem, because softwareupdate does not have a problem installing the update. Therefore nothing will be learnt from the verbose installation of the update, since it will install successfully. The logs from a failed App Store installation of the update will be more useful (however, since the same issue does not occur between DP2 and DP3, I would assume this was fixed).

 

[grahamperrin]

…*nothing will be learnt from the verbose installation of the update …

Please be less dismissive.

In response to feedback (10th July), Apple requested verbose output from a softwareupdate command. The command structure suggested by Apple was different, but the request for verbosity was there.

If you like, ignore the -v and focus on other aspects of the softwareupdate command at step 04 above.

since the same issue does not occur between DP2 and DP3, I would assume this was fixed).

Apple's request came on Friday 11th July and from the nature of that request, I can not make the same assumption about a fix at that time.

 

[tywebb13]

Developers with access to the direct links would probably prefer to update that way if they are having trouble with the mac app store because it is much easier than grahamperrin's way.

I think a public beta program version may become available soon. And what annoyed me about that before with mavericks is that apple did not create any online forum (similar to the developer forums) yet provision was made for it in their public seed agreement. Hence there would be no legitimate means of public beta testers of getting the direct links.

So if apple don't provide such a forum soon, then there probably will be some use for grahamperrin's instructions. I envisage that public beta testers may encounter similar problems that developers did with the DP updates.

I don't doubt that Brian Y may have had more success with the mac app store going from DP2 to DP3 but many other developers still had trouble doing it that way.

The mac app store updates problems for os x betas is actually a very old problem and doesn't seem to be going away soon.

But before it just affected developers who solved it with direct links. Now with the public beta program, it is going to affect many more people who don't yet have the means of accessing such links.

I would slightly modify grahamperrin's instructions though to add 1 more step before updating. Backup the installer pkg first. That way if you have to reinstall, you won't have to go through the process again. Just use the pkg files to update.

 

[grahamperrin]

An Apple-provided forum

… apple did not create any online forum (similar to the developer forums) yet provision was made for it in their public seed agreement. … if apple don't provide such a forum …

Related: https://forums.macrumors.com/showthread.php?p=19352925#post19352925