Did yours do the same as mine for the 12GB download? On my 15" 2017 MBP it went from RC1 to a C build beta then performed a further 800mb download and then it was on RC2. Very strange upgrade path and very time consuming!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Second macOS 13 Ventura Release Candidate to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
I feel this implementation of Continuity Camera for Mac mini and Mac Studio users could easily be overcome by a prompt asking for the Mac password or your Watch can be used to authenticate for use.
Last edited:
Nah I rebooted and grabbed the 1gb update and build version updated. Stopped the 12gb since didn’t seem right
The fact that they needed to issue a second release candidate so soon gives me pause. Apple needs to revert to releasing these things when they deem ready and not on a strict schedule, especially since they're insistent on surprising everyone with the release date reveal less than a week prior to it!
As I pointed out earlier the safari version got updated. Little things caught during the RC can necessitate a RC2 to be sure it's fixed. Thats only 2 days later.
Continuity camera works, if the phone is in horizontal position.
Last edited:
Some people just can't handle any change so when a big change happens they just hate it because it's different.
The other group of haters seem to be those who saw there was a twitter thread by some rando complaining about random bugs in an earlier beta. Gruber chimed in and said something like "these aren't bugs they are systemic problems with SwiftUI that can't be fixed". The vast majority of real issues where then fixed by the next beta...
The update was rapid for me, I think less than 5 minutes from pressing the button to being back to work. This must be a new thing they can apply a new image this quickly
When the first RC candidate came out, I decided to upgrade, and then unenroll. I had tried the beta for about 3 months, and then did a fresh install, and waited until the RC came along.
I could wait until next week, when it will no doubt simply offer an update, but I thought I'd update it through the beta program.
However when clicking the link to download the beta utility; Download the macOS Public Beta Access Utility it comes up with a webpage that says this page 'not found'.
Can someone check that it's just for me, or whether it's legit not being found. I note that on my system, the .bom and.plist files for this utility are still there.
I could wait until next week, when it will no doubt simply offer an update, but I thought I'd update it through the beta program.
However when clicking the link to download the beta utility; Download the macOS Public Beta Access Utility it comes up with a webpage that says this page 'not found'.
Can someone check that it's just for me, or whether it's legit not being found. I note that on my system, the .bom and.plist files for this utility are still there.
You don't need any utility. Open terminal and enter
for Developer Betas or
for Public Betas.
Code:
sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil enroll DeveloperSeedfor Developer Betas or
Code:
sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil enroll PublicSeedfor Public Betas.
You can clearly see what Apple is doing here - trying to bring a similar user experience between Mac OS and iOS. Change is difficult, but I would bet within 6 months no one will be talking about it any more. It's only bad because it's not what we're use to.
My 15” 2017 MBP downloaded a 465MB update to RC2. Are you via developer download or public beta download? I retrieved the developer download.
I woke up to see my 2020 M1 MBP rebooted from a kernel panic, and since then has already crashed/rebooted again. Looking at the Kernel Extensions in backtrace, I'm seeing these two as the culprit:
com.apple.driver.AppleARMWatchdogTimer(1.0)
com.apple.driver.AppleARMPlatform(1.0.2)
I've been reading and going thru all of the crash logs to see what else it could be, I've even uninstalled a few apps thinking I'd see some better performance or at least get rid of the crashes. Can't wait to get a full installer so I can try reinstalling this.
I know others are having zero issues, and this is only my opinion here, but IMO, Hold Out before installing on Monday. Wait until at least Tuesday or Wednesday to make sure more has been addressed. I'd say they need to leave it in the oven a little longer, but maybe they just need to turn the oven on?
****EDIT****
Going even further thru logs and crash reports regarding:
com.apple.driver.AppleARMWatchdogTimer(1.0)
com.apple.driver.AppleARMPlatform(1.0.2)
I'm narrowing this down to this somehow being related to TimeMachine (?) but I'm honestly not sure. I'm no 'Software Dev' but I've been troubleshooting things like this for well over a decade. Sometimes going down the rabbit hole leads to answers, and sometimes just more questions. I've eliminated my USB-C Dock as a potential issue by just not using it at all. I did have a Dell U2717D external monitor (HDMI) along with a WD Passport for Time Machine backups and then a G-RAID 6TB (powered) external drive for storage and media. As I type all this out, though, I'm realizing I could probably use the Apple AV Multiport Adapter I intended to use with my iPad but with my same equipment. For now, though, I'm going to only keep connected to power and not plug anything else in, just to see if/how it crashes again. Because it will. One time I pressed the TrackPad to stop the Screensaver and I was prompted for my fingerprint with the animation for it moving like normal, my Screensaver still going but with the prompt on the screen saying it's waiting to Unlock... Then the TrackPad lost all haptic feedback and turned into a motionless glass plate. All the animations on my screen and TouchBar were still going, though.. Nothing I could do accept a hard reboot or wait for the quick pink flash and crash. I've ran a few Diagnostic Tests, and they all return 'Error Code' ADP000 which means 'No Issues Found'.. So it doesn't appear to be hardware related, and it's also only started since the beta release just before the initial RC (was that macOS 13 b11?). I've stopped using a few apps like iStat Menus and MenuBar Stats. That's helped! I keep my external drives and monitor disconnected, only one crash in 3 days! That's better than the 3-5 I'd have by noon. I keep looking for Apple to update their Dev/Customer/Public web portals to get the link for the Full Installer so I can make a USB Installer and first try installing over itself, which tends to fix a lot. If there's still issues, I'd just wipe it and reinstall again with that same USB Installer.. Having that NOW would be very valuable for testing.
Sorry to all the "Oh man look at THIS long post" folks, I know I've been told I explain things in too much detail (to to to to toDAY Junior!) sometimes.. Hopefully these details will help the few other folks I've seen on here with similar problems like mine. 😓🎃✌️ 🤜 🤛
com.apple.driver.AppleARMWatchdogTimer(1.0)
com.apple.driver.AppleARMPlatform(1.0.2)
I've been reading and going thru all of the crash logs to see what else it could be, I've even uninstalled a few apps thinking I'd see some better performance or at least get rid of the crashes. Can't wait to get a full installer so I can try reinstalling this.
I know others are having zero issues, and this is only my opinion here, but IMO, Hold Out before installing on Monday. Wait until at least Tuesday or Wednesday to make sure more has been addressed. I'd say they need to leave it in the oven a little longer, but maybe they just need to turn the oven on?
****EDIT****
Going even further thru logs and crash reports regarding:
com.apple.driver.AppleARMWatchdogTimer(1.0)
com.apple.driver.AppleARMPlatform(1.0.2)
I'm narrowing this down to this somehow being related to TimeMachine (?) but I'm honestly not sure. I'm no 'Software Dev' but I've been troubleshooting things like this for well over a decade. Sometimes going down the rabbit hole leads to answers, and sometimes just more questions. I've eliminated my USB-C Dock as a potential issue by just not using it at all. I did have a Dell U2717D external monitor (HDMI) along with a WD Passport for Time Machine backups and then a G-RAID 6TB (powered) external drive for storage and media. As I type all this out, though, I'm realizing I could probably use the Apple AV Multiport Adapter I intended to use with my iPad but with my same equipment. For now, though, I'm going to only keep connected to power and not plug anything else in, just to see if/how it crashes again. Because it will. One time I pressed the TrackPad to stop the Screensaver and I was prompted for my fingerprint with the animation for it moving like normal, my Screensaver still going but with the prompt on the screen saying it's waiting to Unlock... Then the TrackPad lost all haptic feedback and turned into a motionless glass plate. All the animations on my screen and TouchBar were still going, though.. Nothing I could do accept a hard reboot or wait for the quick pink flash and crash. I've ran a few Diagnostic Tests, and they all return 'Error Code' ADP000 which means 'No Issues Found'.. So it doesn't appear to be hardware related, and it's also only started since the beta release just before the initial RC (was that macOS 13 b11?). I've stopped using a few apps like iStat Menus and MenuBar Stats. That's helped! I keep my external drives and monitor disconnected, only one crash in 3 days! That's better than the 3-5 I'd have by noon. I keep looking for Apple to update their Dev/Customer/Public web portals to get the link for the Full Installer so I can make a USB Installer and first try installing over itself, which tends to fix a lot. If there's still issues, I'd just wipe it and reinstall again with that same USB Installer.. Having that NOW would be very valuable for testing.
Sorry to all the "Oh man look at THIS long post" folks, I know I've been told I explain things in too much detail (to to to to toDAY Junior!) sometimes.. Hopefully these details will help the few other folks I've seen on here with similar problems like mine. 😓🎃✌️ 🤜 🤛
Last edited:
Will have to test out, in the interim I mounted my old webcam to underneath my desk pointing to the standing desk leg
According to my two iMac M1s running Ventura RC1 (22A379), the update to Ventura RC2 from RC1 was only going to be 570.8MB, but when it downloaded, the size was actually 1.42GB. Then, install after downloading said 30 mins but was actually 3 and a half mins until the Restart prompt and then approx 5 minutes more after Restart until I was back to the Login screen.
Meanwhile, my MacBook Air M2 seems to be stuck on Ventura beta 13.0 (22A5321d) and perpetually claims it is "up to date". Go figure.
I ended up rebooting and getting the 1.42gb update. all is well now on my m1 air.