Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I'm having problems where whenever I log in or restart, OS X is asking me for my iCloud password and then telling me I need an app-specific password for Messages, even though Messages is logged in and iCloud is already working everywhere. When I put it in, it keeps asking for it, and I have to cancel the prompt multiple times before it disappears entirely. It's really frustrating me, and I have no idea what's causing this to happen. I was hoping the new beta would fix it, but I was wrong.

That's related to the new 2 step verification, try generating a new password via Safari. It's automatically generated, you need to copy and paste it. Had this problem on 10.10.3, it's so awful that apple own apps don't support 2 step verification -.-
 
just genuinely curious because I have not been using Photos as much as before on my Mac . . .

I'm really getting frustrated with it, mainly because it's become tedious to export files. If, for instance, I wanted to edit one of my iPhone videos in Final Cut, I could simply drag the video from iPhoto directly into Final Cut. Or if I wanted to edit an image, I could drag it from iPhoto into Pixelmator.

But now, there's no way to drag anything from Photos into another app. You first have to drag it to the desktop (where Photos then makes a copy), then drag it from the desktop into an app. It's insane! My workaround has been to open the Photos library and drill down to the appropriate folder where the original file is located, then drag it in from there.

BTW, FC does have a Photos tab, but when you click it you're simply told, "You must open Photos to see your images" (which of course then can't be imported).

How could Apple have missed something this basic? And over multiple versions!

[Edit: I did notice something interesting. I can drag pictures out of Photos and drop them onto only certain apps (like iTunes and -- oddly -- Handbrake). But most apps including Final Cut will not allow Photos contents to be dropped onto (or into) them.]
 
Last edited:
coreaudiod

Anyone know why coreaudiod is taking up the most CPU on my computer since beta 3? rMBP 15' Late 2013
 
Have you already tested it? I'm hoping some tester will post results from this update.

yes, im having (had) really big wifi problems, response times of 300.000ms and up. used to reset pram etc almost every day. now after updating i have a rocksteady wifi connection.
 
Have you already tested it? I'm hoping some tester will post results from this update.

I had 4 problems:
1) Airplay mirroring from Yosemite was VERY SLOW. Workaround: disable bluetooth on the mac AND on the apple TV
2) Airdrop unreliable and slow: no workarounds
3) corrupted WIFI time machine backups: no workarounds
4) Slow WIFI connection. Workaround: disable and re-enable wifi.

Now...
Problem 1) is not fixed.
I'll test 2-3 and 4 in the next days.
However I have one concern: a single discoveryd process can mess up the whole network, so we will need to wait for an iOS and Apple TV update. iOS devices, including Apple TV, have their own discoveryd implementation
 
Who mentioned Emoji Picker? That swung it for me!

This is why I bought my Mac in the first place - beat that Windows!

Wifi - "it just works" - Windows

Perhaps Apple should decide to be 100% complaint with the Wifi Alliance, which they aren't

----------

I had 4 problems:
1) Airplay mirroring from Yosemite was VERY SLOW. Workaround: disable bluetooth on the mac AND on the apple TV
2) Airdrop unreliable and slow: no workarounds
3) corrupted WIFI time machine backups: no workarounds
4) Slow WIFI connection. Workaround: disable and re-enable wifi.

Now...
Problem 1) is not fixed.
I'll test 2-3 and 4 in the next days.
However I have one concern: a single discoveryd process can mess up the whole network, so we will need to wait for an iOS and Apple TV update. iOS devices, including Apple TV, have their own discoveryd implementation

I suspect there is nothing wrong with your Airplay, Airdrop, and TM, your, or Apples wifi is the root cause
 
I don't get it. Yosemite and all of the betas have been rock solid for me on a non-trivial, 16GB mid-2013 MBP setup (external monitor, multi-OSvirtual machines, wired and wireless networking, multiple memory intensive graphics design, photo and video editing apps, Xcode, even Office for Mac and Office for Windows).

I read the comments before updating and so far I have *upgraded* to every beta without issue. For me, Yosemite remains the best OS I've used -- though I believe Windows 10 is shaping up to be an awesome contender.

Net-net: I sympathize with those who are plagued by Yosemite issues, but the OS has been a stellar performer for me .. and I'm scratching my head for an explanation why some are experiencing the polar opposite.

I find that as well. Re wifi issues, which for Appe, appears to be a staple part of the diet, BAU, etc, I'd love to know the routers that are in use for the that have wifi issues. Apple isn't 100% compliant with wifi, so some routers don't play well with Apple gear.
 
I had 4 problems:
1) Airplay mirroring from Yosemite was VERY SLOW. Workaround: disable bluetooth on the mac AND on the apple TV
2) Airdrop unreliable and slow: no workarounds
3) corrupted WIFI time machine backups: no workarounds
4) Slow WIFI connection. Workaround: disable and re-enable wifi.

Now...
Problem 1) is not fixed.
I'll test 2-3 and 4 in the next days.
However I have one concern: a single discoveryd process can mess up the whole network, so we will need to wait for an iOS and Apple TV update. iOS devices, including Apple TV, have their own discoveryd implementation

I see. This update may not fixed iTunes Home Sharing or Wake On Network request.
 
My setup is not this complex, but is working well on older hardware with no issue. Not sure what the core of folks issues are, but it would be interesting to find out.

I'm curious too. I thought maybe I was being spared by having 16GB RAM; but you're running just fine on 8GB - so that does not support my low memory theory. So far the latest beta feels snappier on Yosemite with Parallels, Windows 8, and Windows 10 beta all running simultaneously with no network issues, no display issues, no speed issues, actually no apparent problems at all.
 
I truly hope this fixes the blurry font issue that has persisted since the beginning of Yosemite
 
Wish I Could

I wish I could try it. But even though I've been using the previous betas of 10.10.4 without issue, I can use this one.

After installing it I can't boot up. I get to the login screen and enter my password, but after the progress bar goes up about a quarter of the way, I get a black screen with a warning symbol.
So now I'm restoring from a Time Machine backup.

Anyone else have this?
 
The odd thing is dragging DOES work for some apps. For instance, I can drag from Photos to Messages, but can't drag from Photos to Twitter.

I already reported this as a bug a couple versions ago, but it hasn't been fixed yet.

But now, there's no way to drag anything from Photos into another app. You first have to drag it to the desktop (where Photos then makes a copy), then drag it from the desktop into an app. It's insane! My workaround has been to open the Photos library and drill down to the appropriate folder where the original file is located, then drag it in from there.
 
Wifi - "it just works" - Windows

Perhaps Apple should decide to be 100% complaint with the Wifi Alliance, which they aren't

----------



I suspect there is nothing wrong with your Airplay, Airdrop, and TM, your, or Apples wifi is the root cause

uhm...you mean the router? I don't think so, unless we are talking about a bug in the firmware. My router is an Airport extreme AC. Apple replaced it for me as I was having so many problems with it. It turned out that with the new router I had the exact same problems. :(
Also Airdrop should work independently from the router.
 
I could see this being true for a Beta, but Photos was released to the general public. That simple (and often used) functionality should have been in it from the beginning.

And I should have won the lottery last week, but I didn't.

Just because you wish something to be true doesn't make it so. Apple clearly said upfront (months upfront) that external editors would not be supported in Photos.

At least not in 1.0.
 
Apple clearly said upfront (months upfront) that external editors would not be supported in Photos. At least not in 1.0.

Right. But that still doesn't make it a rational decision, given that Apple is essentially forcing Photos on all their users. Yes, I could just stick with iPhoto. But since iPhoto has pretty much always supported drag-and-drop onto other apps (as have almost ALL of Apple's apps), I couldn't imagine Photos having next-to-no support for it.

Lets hope things change in future versions.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.