Popping Sound

I see this message Application exceeded audio metadata throttle limit. often for one Stream (live URL), and only when the iPhone is connected to CarPlay. My functionality strongly controls how often the App writes to the property MPNowPlayingInfoCenter.nowPlayingInfo (once in 30 seconds). This screenshot shows logs for the flow: 1 Live is playing 2 users tap on the Stop command on the headunit(CarPlay) 3 I see the message Application exceeded audio metadata throttle limit. 4. Then MPRemoteCommandCenter calls my handler (it contains print with remote Command is called) I have tried to use MPNowPlayingSession, and use a session's remoteCommandCenter, nowPlayingInfoCenter... but the session does not resolve this issue. Often, I see this message even before my app sets any data to MPNowPlayingInfoCenter.nowPlayingInfo (I described this case above). Sometimes I can see a set of these messages (3-6 records). Do you know how to resolve this critical issue? What does Application exceeded audio

I have been trying this procedure on a brand new 2023 MacBook Pro M3 with Sonoma 14.1, and when I try to install the AppleFWAudio pkg, it still gives me a pop-up that it can't be installed because it's from an unknown developer. Am I missing something with that install? When I try the next step (sudo chown ... ) in terminal (in either normal or recovery mode) it says it file doesn't exist. Really hoping I can get this figured out. I have a Mackie 1620 that I enjoy using for drums, and I need the 8 channels. Thanks for any help!

You're in the wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. We're just random people from around the world; we aren't Apple employees. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks. When you ask your question, try to provide more information such as which apps do and do not give a sound; show your sound & haptics settings; show your mute switch setting etc. All that information would be important to pin it down. If you find that there is a bug, you can raise it at: https://feedbackassistant.apple.com/

Hello, Beta releases may take additional disk space to help with testing and bug reporting. macOS Tahoe is also expected to take more space with respect to the UI updates. That said, it sounds like you've get more house cleaning to do or need to consider restoring shipping software. Disk space is a hard limit. If you chose to make more disk space available please take a moment to report this issue with the Feedback Assistant.

So the System was not popping up Do you want to provide access to the Desktop etc folder etc. in this condition to the Standard User. Where did the Message/Window to confirm access to the folder vanish to? There are more questions on this below, but I suspect what's going on here is you have two plugin instances (because Photoshop is running as a separate process in the two different login sessions) which are both talking to the same background process. I don't know how you ended up in that state, but it's impossible for the same process to work in different login sessions. The moment the Admin User was physically logged off the Mac, everything started working for the Standard User even under Screen Sharing. This makes us wonder if this is an edge case macOS bug? No, I don't think this is a macOS bug. Questions I need answered here are these: How are you doing this? Is the background app a launch agent or something else? Also, what exactly is your background app? Is it a true (presumably faceless) ap

Hi J, Thanks for the reply. A little more info: In my specific case, I am indeed using guided generation already (which helped a lot in seed 1 and 2). I thought the eval session was great. I've been working with LLMs for a bit now and it's awesome to have a whole WWDC session to talk about evals and expose them to devs who may not have seen them before. This is coming up for me now because something changed in seed 3 where my feature went from a ~95% success rate to a 0% success rate, all failing with guardrails errors that did not trigger in the first two seeds. There are a bunch of other threads here on the topic and I've filed several feedbacks on the specifics already. Maybe that's a bug/unexpected outcome and we'll see a future seed restore the behavior. I hope so, I'd like to ship this feature. But if not, at least I won't have sent it to customers. My real concern is that in a future point release where the amount of feedback time is compressed and IMO it's very hard to get specific issues in front of

First of all, thank you for the answers. We went back and figured exactly what was occurring and the condition. Everything we did when I posted my original message was on a newly setup M4 Pro Mac with 15.5 as we like to test things continuously. To investigate further we setup a VM with the same conditions Admin user/Standard user. On the VM everything was working under the Standard user account wherein the System did pop up message saying Do you wish to grant ABCD access to the Desktop or Downloads etc folder. We grant access and our plug-ins work as expected. We went back to the actual M4 Pro machine and understood exactly what was occurring. The Admin user was Physically logged into the system though the GUI was not in use. But the Standard User for testing purposes was logging in via Screen Sharing to the M4 Pro Mac. So the System was not popping up Do you want to provide access to the Desktop etc folder etc. in this condition to the Standard User. Where did the Message/Window to confirm

Hello, It sounds like you've followed the correct steps to connect your Vision Pro in developer mode. Note that enabling Developer Mode typically requires rebooting the Vision Pro so be sure to do that. Likewise, to err on the side of caution, try rebooting the Mac and restarting Xcode. If you're still having issues send us a bug report with a sysdiagnose (Mac and Vision Pro) taken when you attempt to build and deploy your app from Xcode. You may also want to consider purchasing a developer strap for a USB-C connection to the Mac.