jup, but have had that since Monterey.Does anyone else have networking problems where you'll connect to wifi but not actually route traffic?
jup, but have had that since Monterey.Does anyone else have networking problems where you'll connect to wifi but not actually route traffic?
Like?Well whatever, but I'm not alone in hating the new one.. And there are countless little things that just don't work right in the sub menus. many things aren't even visible until you start right clicking on certain items.
This one is fixed for me in beta 6.Tha
The powered bug is the top of my wish list. My 2019 16" MacBook Pro is about to take off from my desktop. Thankfully there is a temporary fix online. But the script has to be run after every restart.
sudo pmset schedule cancelall
Isn’t this just on a restart and last for 4 minutes tops as Spotlight associated programs do an entire system wide scan. I’m pretty sure this is normal behavior as in that’s how MacOS has always operated, no?Hopefully some of the powerd and mds_stores (spotlight)
Isn’t this just on a restart and last for 4 minutes tops as Spotlight associated programs do an entire system wide scan. I’m pretty sure this is normal behavior as in that’s how MacOS has always operated, no?
Give your machine 5 minutes give or take and then check system cpu usage.
So far I am not seeing the same with beta 6.Hopefully some of the powerd and mds_stores (spotlight) occasionally hogging CPU issues are addressed.![]()
Just did a clean install of Beta 6, everything smooth so far. I'll install CCC and give that a try soon.So far I am not seeing the same with beta 6.
CCC backups with spotlight hogging the CPU would cause the 4th step (create/copy data volume) to fail in beta 5, appears to be fixed in beta 6.
This is on a M1 24" iMac and a 16" M1 Max MBP. Hope it works better for others here.
That's wonderful that they've fixed that issue with the VPNs. I was able to use Wireguard in the meantime so it wasn't an issue remotely. That sucks about Billings Pro!Beta 6 finally(!) fixes the various VPN issues. In Betas 1-4 you couldn't connect to any L2TP VPNs, nor could you create new ones. In Beta 5 you could finally connect to the VPNs, but the interface to create new ones was rather screwed up (as a result of the new System Settings). In Beta 6 everything is now working! This is probably not a big deal for most people, but it was a huge deal for anyone who uses VPNs to connect to work offices.
The biggest issue for me now is that my invoicing software (Billings Pro) isn't working properly. Alas, that's not really an Apple issue, so no idea if that will ever get fixed.
How do you close that extra window? Do you close it by clicking the red × button (or ⇧⌘W), or by closing its empty tab with ⌘W? Try closing the tab rather the window. Otherwise, Safari will diligently reopen that closed window (which still had an open tab in it) the next time you launch it.Is it just me who's experiencing Safari opening an extra blank window when you quit and open with "All windows from last session" enabled?
It's driving me insane and doesn't happen on Monterey.
I had that problem with Beta 4, but installing Beta 5 fixed the issue. macOS has some annoying intermittent device-discovery issues that only seem to resolve themselves when you update the OS. For instance, my HomePods occasionally disappear from the Sound menu (but not from Home) after a reboot, and I can no longer use them as external speakers until the next OS update.I just wish unlock with Apple Watch would work again, I have not been able to unlock with Apple Watch since Ventura Beta 1. Still works on my MacBook on Monterey.
I have tried everything including resetting Bluetooth, wifi, signing out and back in to Apple ID and creating new user to no avail.
Didn’t work! It still opens an extra window. It worked fine until Monterey. The issue is with Safari 16 and not Ventura itself. Downloaded the beta of Safari 16 for Monterey before I upgraded to Ventura beta and had the same thing happen before. I’m losing my mind.How do you close that extra window? Do you close it by clicking the red × button (or ⇧⌘W), or by closing its empty tab with ⌘W? Try closing the tab rather the window. Otherwise, Safari will diligently reopen that closed window (which still had an open tab in it) the next time you launch it.
That is bizarre. You could try closing all your tabs across all windows, if that is feasible (first save them all as bookmarks, maybe); or transfer them all into the window with the empty tab (you can drag tabs between windows).Didn’t work! It still opens an extra window. It worked fine until Monterey. The issue is with Safari 16 and not Ventura itself. Downloaded the beta of Safari 16 for Monterey before I upgraded to Ventura beta and had the same thing happen before. I’m losing my mind.
Bizarre indeed! Even more weird would be the issue only happening if I'm quitting a Private window. Private is my default but tried opening a few tabs in regular window and Cmd+Q and then reopened Safari. It opens just the window as it should and no extra windows.That is bizarre. You could try closing all your tabs across all windows, if that is feasible (first save them all as bookmarks, maybe); or transfer them all into the window with the empty tab (you can drag tabs between windows).
No, if it is the issue I have the symptom is that Spotlight does not work at all. Rebuilding the cache does not work, but creating a new user does. Haven’t installed the latest seed yet, but fingers crossed.Isn’t this just on a restart and last for 4 minutes tops as Spotlight associated programs do an entire system wide scan. I’m pretty sure this is normal behavior as in that’s how MacOS has always operated, no?
Give your machine 5 minutes give or take and then check system cpu usage. 🙂
This new System Settings app is really terribleAny major improvements to the horrible new System Settings?
Does the Beta 6 include the important security fix from 12.5.1?AppKit
CoreGraphics
Deprecations
- To improve security, CGImageCreate enforces parameter correctness on macOS 13 Ventura, iOS 16, iPadOS 16, watchOS 9, and tvOS 16. Passing an incorrect CGImageByteOrderInfo is no longer supported, and will result in images failing to load. (94855401)
DeviceDiscoveryUI
Known Issues
- Devices running beta 4 or later aren’t backwards compatible with devices running earlier beta versions. (95233878)
Mail
Resolved in macOS 13 Ventura beta 6
- Fixed: Highlighted search snippets might stay visible after closing search. (91830631)
Known Issues
- Moving a Remind Me message to another mailbox doesn’t remove the Remind Me banner. (93685824)
Metal
Known Issues
- The MTLResource.gpuHandle is deprecated. (92862429)
Workaround: Use gpuResourceID instead, which functions as a replacement.Metal Offline Compiler
Known Issues
- MetalFX effect outputs aren’t designed to be consumed by the CPU. Outputting to a texture that is read only by the CPU might result in synchronization issues. (91515075)
Workaround: If a CPU reading of the MetalFX output is desired, instead of encoding the MetalFX effect as the last item in a command buffer, encode a dummy blit that consumes the MetalFX output texture (a 1-pixel region blit is fine) in the command buffer. After the command buffer with the dummy blit is finished, reading of the MetalFX effect output texture with CPU synchronizes correctly.Networking
Deprecations
- FTP is deprecated for URLSession and related APIs. Please adopt modern secure networking protocols such as HTTPS. (92623659)
Security
Known Issues
- You might encounter multiple prompts asking for user consent to manage apps when installing and upgrading apps. (94192721)
Software Update
Resolved in macOS 13 Ventura beta 6
- Fixed: You might be unable to update to macOS 13 Ventura beta from macOS 11 Big Sur. (98338957)
Stage Manager
Known Issues
- With Stage Manager active, windows continue as the key window and receive key events when minimized. (94169311)
StoreKit
Deprecations
- Deprecated the SKDownload API and removed the option to upload nonconsumable in-app purchase assets for Apple to host. In addition, support for managing these assets in App Store Connect is no longer available as of April 2022. (89764253)
Swift
Known Issues
- Network.framework resolved an issue that could cause NWBrowser, NWConnection, NWConnectionGroup, NWEthernetChannel, NWListener, and NWPathMonitor to trigger a retain cycle when various Handler blocks are set. Starting with macOS 13, iOS 16, watchOS 9, and tvOS 16, if software using Network.framework targets these releases as the minimum OS, the object releases any blocks they captured once cancelled, breaking the retain cycle. (89677097)
Workaround: For software targeting older versions, the retain cycle can be broken by setting the handler blocks to nil after canceling the object.SwiftUI
Known Issues
- Providing actions to a navigationTitle modifier has been deprecated. Use the toolbarTitleActions() modifier or ToolbarTitleActions type in a toolbar modifier instead. (93658035)
Texts and Fonts
Deprecations
- ATS and ATSUI APIs are fully deprecated. Code using these APIs will fail to compile and link when the deployment target is set to 13. Code targeting earlier versions of macOS will continue to compile, link, and run. macOS 13 is the last release where code depending on ATS or ATSUI will run. All runtime functionality will be removed in next major release of macOS. (83581159)
Wallet
Known Issues
- American Express cards might need to be removed and re-added to Wallet after updating to macOS 13 beta 6 or later. (97990752)
I was wondering who re-designed that new UI? did they really use it themselves???Any major improvements to the horrible new System Settings?