if you look a few posts up you will see for me still not fixed.Hi, does anyone know if the CarPlay issues w this beta were fixed in this updated release? That’s the only thing keeping me from this beta. Thanks!
I had had no issues with this updated beta, or the previous one, using wireless CarPlay via CarPlay2Air in an Audi.Hi, does anyone know if the CarPlay issues w this beta were fixed in this updated release? That’s the only thing keeping me from this beta. Thanks!
Uh... the notifications WILL go to your Notification Center, so, it's correct.Is this worded incorrectly? Should the word NOT be in there when talking about the notifications “will not appear”
![]()
It's worded correctly. Notifications will be in the Notification Center and not shown on the Lock Screen.Is this worded incorrectly? Should the word NOT be in there when talking about the notifications “will not appear”
It’s only some vehicles. Ford primarily but maybe some others.I had had no issues with this updated beta, or the previous one, using wireless CarPlay via CarPlay2Air in an Audi.
Yep, one revision after the previous releasedReason this is a K build is because it was compiled once more with the minor changes I assume? Therefore taking it from J to K?
This is too funny to be not sarcasticBecause I'm not enabling and leaving on wifi—exposing myself to yet more electromagnetic radiation pollution and less importantly degrading the Watch's longevity—just to be able to use some half-assed feature like this one! 😄
Looks like it's a Ford thing...I had had no issues with this updated beta, or the previous one, using wireless CarPlay via CarPlay2Air in an Audi.
I fully understand that. But saying it’s a mistake makes it even more ridiculous. Who would NOT notice these things during a proper QA process. I notice this stuff within a day or even less. Also the point of public betas was to have LESS of these kinds of issues overall, not more.Without wishing to wade in on your micro argument.. ‘bugs’ like the white text on a while background may not be recognised as a bug and it’s simply a mistake that hasn’t yet been corrected. If you’re one of a handful of people noticing it and reporting it, it’s unlikely to be picked up quickly.
Fixed with today’s updateNope. This appears to have been corrected.
Also the point of public betas was to have LESS of these kinds of issues overall, not more.
Although it’s new to you, it’s not new to this beta 😅My favourite new feature is no more typing in my Apple Watch code every morning.
Now when I unlock my phone it unlocks the Watch as well, clever stuff!
My favourite new feature is no more typing in my Apple Watch code every morning.
Now when I unlock my phone it unlocks the Watch as well, clever stuff!
It’s unlikely that Apple would drop support for a device in a minor 14.X update. For several years now, they’ve dropped support during major releases. At most, they continue supporting older devices but make newer features exclusive.Dude, I'm not having an issue with a beta. It literally won't install on *stock* watchOS...
That’s been out since the very first Apple Watch!My favourite new feature is no more typing in my Apple Watch code every morning.
Now when I unlock my phone it unlocks the Watch as well, clever stuff!