I report here some messages from Apple Community for an untracked bug in macOS Sonoma (from 14.0 to 14.2 beta 4 at the time). https://discussions.apple.com/thread/255214328 Original message 1: I've finally noticed a pattern that occurs rather frequently on macOS Sonoma. I was blaming Bluetooth issues before, but it looks like it's more about audio in general. What happens is that at some point, all audio freezes. The hotkeys for the audio controls show "Stop" sign, like there are no audio outputs connected, the taskbar is completely unresponsive: Control Centre shows a spinning circle, the sidebar is not opening (Spotlight works, though). If you go to the System Settings, some menu items will be unresponsive: Sound doesn't open, Bluetooth does not open, Accessibility and Siri & Spotlights all do not open. Then, a new bug appeared that I've just started to notice recently. The screen is flashing like there's an Accessibility feature enabled that uses warning flash instead of sound. It appears just randomly, out of nowhere. Immediately after that, sound works just normally. When this is happening, and video/audio content in the browser and wherever does not work, Tidal shows many random errors, and Firefox just completely hangs when you try to play a video on YouTube. I've tried to stop coreaudiod and it did restart the daemon, but nothing else happened. The device is a very fresh M1 Max MacBook, and nothing like that was happening on Ventura. I've had audio cracks on another M1 Pro laptop, but this one didn't even have those. P.S. This is happened just when I was writing this post, and I've disabled Bluetooth just before. Now, the Bluetooth section in the Settings is opening, but others are still unresponsive. For reference - I have yabai and BetterSnapTool installed, which modify system behavior, but with system protection enabled. Siri is disabled. I've tried to stop a bunch of random processes when this happened, but none helped so far. This issue constantly haunts me since I've upgraded, and it's extremely annoying. Original message 2: Yes, I'm thinking it's a combination of Bluetooth and audio issues. I've got all apps that are trying to use audio crashing after I'm just connecting my Bluetooth earbuds. Now I see that the coreaudiod is just not running this time - I've tried to connect to a Slack Huddle, and it just hanged, sound is unresponsive again and the Settings app is not working as I mentioned before. I've checked the Activity Monitor and found that the process that works with audio on macOS (coreaudiod) is not running. I've attempted to launch coreaudiod with sudo launchctl load /system/library/launchdaemons/com.apple.audio.coreaudiod.plis, and got Load failed: 5: Input/output error as a response. After a while, when I disabled the earbuds it's started again on its own and coreaudiod is running, and the audio controls are working once more. Original message 3: Just accidentally looked at the Console App while looking for logs for other things, and found out that my codeaudiod crashing by cooldown every day 10 to 50 times with intervals from 1 second to a couple of hours, around 5 minutes on average. The crash is the following: Crashed Thread: 18 Dispatch queue: com.apple.audio.device.~:AMS2_StackedOutput:0.event Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 I also found that avconferenced fails too occasionally, though very rare - I believe that's the process that connects iPad as a second screen, and it _too fails with sigsegv on 0x0 - though not that it's some unique bug to attempt to read memory at 0, maybe just a coincidence. @Flomaster do you use Sidecar by chance? My message: I too have this problem on my MacBook Pro M2 Pro since upgrading to macOS Sonoma. It mainly occurs with AirPods Pro 2 but I have also had this happen to me using OnePlus Buds. The blockages are the same as you have experienced and, as I often work in video conferences, blocking MS Teams or Google Meet is really becoming a serious problem. Desperate, I tried installing macOS Sonoma 14.2 beta but none of the updates solved the problem. I even tried a full restore, re-importing the data from Time Machine but to no avail. Indeed, with Beta 4 the problem seems to have worsened because the AirPods now even struggle to connect.

This evening iOS 17.3 Beta 2 is available for download and installing. After the Update my iPhone won't start anymore. Apple symbol is visible, after some seconds wait symbol flashes up 2-3 times and then disappears. Screen stays black and phone is not accessible anymore.

I have been using the HomePod 17.3 Beta for while and wanted to reset it yesterday. Now I can not set up both my HomePods (one OG and one Mini) anymore. Setup with iPhone and iPad keeps failing after 2 minutes. When the Mini is plugged into the Mac and I click "restore" I get an error message "Update server could not be contacted". Any idea?

I would like to move my external beta testers to another one of my apps. Is this possible or do I have to manually enter each one again manually as a tester for my other apps?

Has anyone experienced Touch ID no longer working on Magic Keyboard after installing 14.3? It's almost as if the Mac doesn't understand there is a reader on the keyboard because I don't get the fingerprint image anymore when it's asking me for it. Touch ID works fine when I am using the built-in reader, but I normally have my Macbook closed and use the Magic Keyboard.

Hi, I am using the Apple TV application on a computer with Windows 10. For some time now I have had problems with playing video material. It often happens that there is a black screen in the background, there is sound playing and at some point the entire application freezes. only restarting the computer will help. I was looking for a solution on the Internet and found that many people had a similar problem. The second problem is that the video cannot be played at all, and video clips do not work in the Apple Music application. Only resetting the application helps. The attached video shows a problem with displaying subtitles embedded in the movie "An Apple Original", this problem does not occur in trailers, etc. This can be seen at the end of the trailer where the inscription "December 15 ", he just doesn't blink. I would like to point out that this effect does not occur when I watch it through the Chrome browser. I use the application because it is possible to download a movie/series to disk, which allows me to eliminate any overdubs and jams by streaming directly. From what you can see, both applications are in the beta, preview phase. Have any of you had similar problems? Where can I report it so that developers (I don't know if it's Apple or Microsoft) eliminate it? So when will both applications be released in their final version? https://photos.app.goo.gl/1zuyLS5KjGhSRHM87 Thank you in advance for your answer and help. Regards.

Hi, I get anytime crash on the Settings app for iPhone 15 Pro and iPhone 15 Pro Max on Xcode 15 RC. Translated Report (Full Report Below) Incident Identifier: DE1BE6D0-4367-4203-A339-1AE20D50218A CrashReporter Key: 1A043114-8ED1-1A39-B80C-A3825853E7D7 Hardware Model: MacBookPro18,2 Process: Preferences [80787] Path: /Library/Developer/CoreSimulator/Volumes/iOS_21A328/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.0.simruntime/Contents/Resources/RuntimeRoot/Applications/Preferences.app/Preferences Identifier: com.apple.Preferences Version: 1 (1246.2) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd_sim [80318] Coalition: com.apple.CoreSimulator.SimDevice.A989B9A5-9C97-40A3-9082-998713FB7EAB [9443] Responsible Process: SimulatorTrampoline [51087] Date/Time: 2023-09-13 16:09:55.5678 +0300 Launch Time: 2023-09-13 16:09:53.8486 +0300 OS Version: macOS 13.5.2 (22G91) Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: Preferences [80787] Triggered by Thread: 10 Last Exception Backtrace: 0 CoreFoundation 0x18046589c __exceptionPreprocess + 160 1 libobjc.A.dylib 0x18005c09c objc_exception_throw + 56 2 CoreFoundation 0x180350b68 -[__NSPlaceholderArray initWithObjects:count:] + 552 3 CoreFoundation 0x1804508b8 +[NSArray arrayWithObjects:count:] + 36 4 ActionButtonSelector 0x127b6c5ac ABLoadDeviceSceneModel + 2280 5 ActionButtonSelector 0x127b677e4 -[ABDeviceSceneResourceLoader _loadResources] + 68 6 ActionButtonSelector 0x127b673f0 __59-[ABDeviceSceneResourceLoader loadResourcesWithCompletion:]_block_invoke + 40 7 libdispatch.dylib 0x1801424f4 _dispatch_call_block_and_release + 24 8 libdispatch.dylib 0x180143d3c _dispatch_client_callout + 16 9 libdispatch.dylib 0x18014be3c _dispatch_lane_serial_drain + 960 10 libdispatch.dylib 0x18014c9b4 _dispatch_lane_invoke + 388 11 libdispatch.dylib 0x180157d40 _dispatch_root_queue_drain_deferred_wlh + 276 12 libdispatch.dylib 0x18015738c _dispatch_workloop_worker_thread + 448 13 libsystem_pthread.dylib 0x1062e3878 _pthread_wqthread + 284 14 libsystem_pthread.dylib 0x1062e263c start_wqthread + 8 Thread 0:: Dispatch queue: com.apple.shortcuts.VCVoiceShortcutClient.InternalState 0 libsystem_kernel.dylib 0x1063c91d0 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x1063da298 mach_msg2_internal + 76 2 libsystem_kernel.dylib 0x1063d13d8 mach_msg_overwrite + 540 3 libsystem_kernel.dylib 0x1063c9540 mach_msg + 20 4 libxpc.dylib 0x1800a9b2c _xpc_pipe_mach_msg + 52 5 libxpc.dylib 0x1800a9028 _xpc_pipe_routine + 396 6 libxpc.dylib 0x180089e60 _xpc_interface_routine + 168 7 libxpc.dylib 0x18008a4a0 _xpc_look_up_endpoint + 264 8 libxpc.dylib 0x1800923e4 _xpc_connection_bootstrap_look_up_slow + 296 9 libxpc.dylib 0x180095174 _xpc_connection_init + 724 10 libxpc.dylib 0x180092a8c _xpc_connection_activate_if_needed + 300 11 libxpc.dylib 0x180093cd4 xpc_connection_resume + 92 12 VoiceShortcutClient 0x196b0ebf8 -[VCVoiceShortcutClient unsafeSetupXPCConnection] + 308 13 VoiceShortcutClient 0x196b10554 __81-[VCVoiceShortcutClient asynchronousRemoteDataStoreWithErrorHandler:synchronous:]_block_invoke + 200 14 libdispatch.dylib 0x180143d3c _dispatch_client_callout + 16 15 libdispatch.dylib 0x180153dc8 dispatch_sync_invoke_and_complete_recurse + 96 16 libdispatch.dylib 0x180153778 dispatch_sync_f_slow + 188 17 VoiceShortcutClient 0x196b0e584 -[VCVoiceShortcutClient asynchronousRemoteDataStoreWithErrorHandler:synchronous:] + 156 18 VoiceShortcutClient 0x196addb44 -[VCVoiceShortcutClient(Staccato) fetchAvailableStaccatoActions:] + 92 19 ActionButtonConfigurationUI 0x10549c2d0 0x105488000 + 82640 20 Combine 0x19e00dbd8 specialized Future.init(:) + 224 21 Combine 0x19e00b4a0 Future.init(:) + 20 22 ActionButtonConfigurationUI 0x1054a295c 0x105488000 + 108892 23 ActionButtonConfigurationUI 0x10549837c 0x105488000 + 66428 24 PreferencesUI 0x104bd7c3c 0x104bb0000 + 162876 25 PreferencesUI 0x104bc5b54 -[PSUIPrefsListController tableView:cellForRowAtIndexPath:] + 260 26 UIKitCore 0x114e3dfc4 -[UITableView _createPreparedCellForGlobalRow:withIndexPath:willDisplay:] + 1376 27 UIKitCore 0x114e11134 -[UITableView _updateVisibleCellsForRanges:createIfNecessary:] + 560 28 UIKitCore 0x114e1174c -[UITableView _updateVisibleCellsNow:] + 1112 29 UIKitCore 0x114e2b53c -[UITableView layoutSubviews] + 144 30 UIKitCore 0x115126b1c -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1492 31 QuartzCore 0x1884d3dd4 CA::Layer::layout_if_needed(CA::Transaction*) + 440 32 QuartzCore 0x1884deb30 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 124 33 QuartzCore 0x1883fa3bc CA::Context::commit_transaction(CA::Transaction*, double, double*) + 460 34 QuartzCore 0x188429bf0 CA::Transaction::commit() + 652 35 UIKitCore 0x114c2c504 __34-[UIApplication _firstCommitBlock]_block_invoke_2 + 32 36 CoreFoundation 0x1803c6464 CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK + 20 37 CoreFoundation 0x1803c5bac __CFRunLoopDoBlocks + 352 38 CoreFoundation 0x1803c0450 __CFRunLoopRun + 788 39 CoreFoundation 0x1803bfd28 CFRunLoopRunSpecific + 572 40 GraphicsServices 0x18986ebc0 GSEventRunModal + 160 41 UIKitCore 0x114c13fdc -[UIApplication _run] + 868

Just now, I accidentally deleted Xcode15.1 Beta3. Now I want to download it again, but I found that Xcode 15.1 Release Candidate replaced Xcode15.1 Beta3 in https://developer.apple.com/download/applications/, but there is no visionOS SDK in Xcode 15.1 Release Candidate, so I really need to download Xcode15.1 Beta3 now. Who has any way for me to download it again?

When using Xcode 15 beta 8 / iOS 17 beta 8 simulator runtime, we can see in Activity Monitor that memory used by "SimRenderServer" proccess grows significantly with each UI test run. It reproduces even on an empty test, that just wait for a second without launching the application. Memory usage doesn't go down when test run finishes, so each consecutive run adds more to it. For example, create an new project with a UI test // The contents of the test don't actually matter func testExample() async throws { try await Task.sleep(for: .seconds(1)) } Run this test repeatedly 100+ times and observe the "SimRenderServer" process in the Activity Monitor. From what we observed it only reproduces when "Preferred Capture Format" in the test plan configuration is set to "Video". Setting it back to "Screenshot" does no result in growing memory usage. This was reproducible on macOS Sonoma beta / macOS Ventura 13.5.1. Feedback was submitted FB13098749.

I'm looking for build versions as and when iOS gets their latest versions. Needed them for compliance policies.

I originally installed TestFlight.app using a different AppleId (AppleId-A) than what I am currently logged in with (AppleId-B via Settings) on my phone. To improve the app update experience (i.e. not have to supply the AppleId-A password every time) I removed the app and re-installed using AppleId-B and now TestFlight.app requires an invitation redeem code to continue. I am a developer with access to our TestFlight dashboard and I cannot find a way to generate a redeem code or invite link for my AppleId-B user. I can remove myself from internal groups but re-adding does not give me a code or a link. How can I restore the ability to install TestFlight builds again on my phone? Thanks, Jim

I am facing an Issue when trying to install an app using xcrun devicectl device install app command. Command used xcrun devicectl device install app /tmp/avinash/Payload/Sample iOS.app --device <deviceid> Error thrown code-block15:27:24 Acquired tunnel connection to device. 15:27:24 Enabling developer disk image services. 15:27:24 Acquired usage assertion. ERROR: Failed to install the app on the device. (com.apple.dt.CoreDeviceError error 3002.) NSURL = file:///tmp/avinash/Payload/Sample%20iOS.app/ -------------------------------------------------------------------------------- ERROR: The item at Sample iOS.app is not a valid bundle. (com.apple.dt.CoreDeviceError error 3000.) NSURL = file:///tmp/avinash/Payload/Sample%20iOS.app/ NSLocalizedFailureReason = Failed to get the identifier for the app bundle. Temporary fix Rebooting the host machine fixes the issue but it reappears after some time. Related system log generated during app installation kernel: (Sandbox) /Library/Developer/PrivateFrameworks/CoreDevice.framework/Versions/A/XPCServices/CoreDeviceService.xpc/Contents/MacOS/CoreDeviceService exhausted sandbox memory capacity; may be leaking extensions kernel: (Sandbox) Sandbox: CoreDeviceService(8658) deny(1) file-read-data /tmp/avinash/Payload/Sample iOS.app Another potential temporary solution can be: releasing the sandbox memory. How this can be achieved? How can be sandbox memory cleared? What can be the permanent solution for this issue? I tried clearing derivedData folder but didn't help.

Hi Team - we are publishing an app from Azure pipelines and receiving an error "Error: 'What to Test?' is required when using 'Distribute to External Testers'." I have tried providing a file name at GitHub "releaseNotes.txt" and the raw data. nothing worked out. Please help me with this. what needs to be configured in the release notes option?

Ever since updating to watchOS 10, my series 7 Watch with Cellular and no active plan has been experiencing major battery drain issues. After receiving full charge, the battery is drained completely within about 3-4 hours, which was not the case prior. There was no noticeable change with the 10.1 public update which mentioned specifically that it resolves issues with some users experiencing rapid battery loss. Being so disappointed, I submitted an issue report to Apple with the details including the fact that the battery health percentage was at 87%. (Don’t know what it was prior to the v10 update). My frustration with the problem then led me into enabling beta updates for my watch and I proceeded to install the beta version 10.2 as I saw users in some forums stating it resolved their issues. Needless to say, after updating, the watch worked normally for a few hours, noticed it was dead, put it to charge (with a known working charger), and now it’s been several days in which it does not turn on no matter the combination of button presses or state of charging. The only indication of life I see is that sometimes a visual of the charging puck with a red voltage symbol appears when I place it to charge. It doesn’t boot whether I leave it charging over night or just sitting there. This is the first time I’ve been dissatisfied with an update released by Apple. Now I have to go out of my way to get it working again. Would love any suggestions before I am forced to go speak to a Genius...

Not sure if this code is supposed to leak memory or am I missing something? import SwiftUI import Observation @Observable class SheetViewModel { let color: Color = Color.red init() { print("init") } deinit { print("deinit") } } struct SheetView: View { @State var viewModel = SheetViewModel() var body: some View { Color(viewModel.color) } } @main struct ObservableMemoryLeakApp: App { @State var presented: Bool = false var body: some Scene { WindowGroup { Button("Show") { presented = true } .sheet(isPresented: $presented) { SheetView() } } } } Every time the sheet is presented/dismissed, a new SheetViewModel is created (init is printed) but it never released (deinit not printed). Also, all previously created SheetViewModel instances are visible in Memory Graph and have "Leaked allocation" badge. Reverting to ObservableObject/@StateObject fixes the issue, deinit is called every time the sheet is dismissed: -import Observation -@Observable class SheetViewModel { +class SheetViewModel: ObservableObject { - @State var viewModel = SheetViewModel() + @StateObject var viewModel = SheetViewModel() Does this mean there's a bug in Observation framework? Reported as FB13015569.

I have an app that has an iOS, Widget and ShareExtension targets. When viewing the project file and I look at the iOS target, it has the Identity section I can view / change the app category, Display Name, Bundle Identifier, version and build. However, the Widget and ShareExtension now has these missing. So, if I try to change the iOS version / build I get an error that they do not match. The data appears to exist in the project file so I can hand edit the file for the Widget and ShareExtension. I believe this started since using the Xcode 15 betas. Or at least I haven't noticed until now since I wanted to change the version number. This appears to be consistent across all projects I have with Widgets. Has anyone experienced this and is there a way to get it back?

The application does not work on Xcode 15.0.1, only on Xcode 15.1. But I can't upload it to the Apple Store because Xcode Beta is not supported. I uploaded it with Xcode 15.0.1 to the Apple Store, but on older iPhones it even opens the LaunchScreen and closes the app. I tried debugging using Xcode 15.0.1 and the same behavior happens. It works in Xcode 15.1, but there's no way to use Xcode 15.1 because Apple doesn't accept it.

We're building one of our iPad apps for "Apple Vision Pro (Designed for iPad)" simulator and need to have certain different build settings for that simulator variant, compared to the default iOS simulator variant. It seems both variants use the iphonesimulator SDK. And in the Xcode build settings, the "Any iOS Simulator SDK" variant of any setting is what is also used, even when building for "Apple Vision Pro (Designed for iPad)". We tried adding a variant to the "Any iOS Simulator SDK" variant for one of the settings by editing the project file directly, using some possible variants we could think of. The added variant does show in the Xcode UI but it shows as "Any iOS Simulator SDK" also. But when building for "Apple Vision Pro (Designed for iPad)" Xcode still uses the original variant, as if it doesn't see that the added variant is matching the build destination. Example, where we want to exclude arm64 for iOS simulator builds, but not for "Apple Vision Pro (Designed for iPad)" builds. Original "Any iOS Simulator SDK" variant: "EXCLUDED_ARCHS[sdk=iphonesimulator*]" = "arm64"; Added variant: "EXCLUDED_ARCHS[sdk=iphonesimulator*][variant=Apple Vision Pro]" = ""; We have tried using variant names such as 'xr', 'xors', 'vision', 'visionos' and of course 'Apple Vision Pro' to no avail. The variant shows in the UI but the build doesn't use it. Does anyone know if there is a variant (or other property or other way of distinguishing such variant) that we can use that Xcode will recognize and use when building for "Apple Vision Pro (Designed for iPad)"? Thanks.

How can I detect the StandBy mode on iOS 17? When my widget is used in StandBy mode, the background is removed thanks to this method: .containerBackground(for: .widget) { myBackgroundImage() } This is very useful when my small widget is displayed on the iPad Lockscreen in landscape mode for example. But to delimit my widget frame on the iPad lockscreen I set up an alternative light background this way: if widgetRenderingMode == .vibrant { Color.white.opacity(0.1).cornerRadius(cornerRadius) } My question: How to add the same alternative background when the widget is used in StandBy mode? In StandBy mode, widgetRenderingMode is equal to .fullColor like on the HomeScreen. But I want to be able to add this background only in standBy mode... Precision: containerBackground(for: .widget){} send it's content to the background of the container so I can't hide my light background behind it as it will always be in front wherever I put it...

Something significant changed between MacOS 14.2b1 and the subsequent betas of 14.2. Photoshop, which has been running fine up to the first beta, suddenly refuses to run. The splash screen shows and then the application dies. I've been in communication with Adobe about this, and from the logs they can see that the problem is with MacOS. While this is not a crisis for me since I have three other machines running either 14.2b1, 14.1.1 and 14.1.1, I can complete my tasks, but this is an annoying problem. Attached is a log from beta 3 just to illustrate the problem. ACPL__2023-11-09_22-40-47.131385Z_00.log Just for the record, what is the most efficient way to roll back to the current released version of Sonoma. I've got multiple system backups, so restoration isn't an issue. Just looking for an approach that doesn't require half a day if possible.