Popping Sound

Sorry, let me better explain what I meant, I typed it incorrectly in the previous post. For some additional context, we build web browsers so it's very normal for us to be running a local web server during UI/integration testing to provide web pages to test certain features with while ensuring we're not hitting the network directly to get better determinism in our tests. Here's a truncated diagram of our system architecture for CI today: [root] launchd ↳ [user] ~/Library/LaunchAgent/github.actions.runner.plist ↳ [user] xcodebuild ... test What I've prototyped is not actually moving the agent to a daemon (this is not possible due to the requirements that GitHub's runner software has. Instead, I'm proposing that we run the xcodebuild ... test command with sudo. This would modify our architecture slightly to look like this when, and only when, we run the testing job. [root] launchd ↳ [user] ~/Library/LaunchAgent/github.actions.runner.plist ↳ [user] sudo xcodebuild ... test This means we have to add xcodebuild to

We also face this issue. We are using AVAudioEngine for audio playback and manually control MPNowPlayingInfoCenter. We use AVPlayer for some silent background videos in app but when doing so the video player controls the playbackState with no way to opt-out. After filing a DTS, feedback and lab I am fairly sure there is no solution for this currently unfortunately. I filed FB9837867 and am crossing my fingers for some progress. Our current work-around which is not ideal is to set MPNowPlayingInfoCenter.default().nowPlayingInfo = nil whenever we pause the audio playback. This seems to somewhat work but also has some other not great side-effects. @Rodrigue2g Did you find any better solutions since posting this? I would encourage you to file feedback and mention FB9837867 as well!

[quote='843215022, Darrilla, /thread/787020?answerId=843215022#843215022, /profile/Darrilla'] The problem is that when I try to export it, I get “An invalid key was encountered” [/quote] Hmmm, that’s weird. I’m not sure what’s causing that, but its sounds like something you’d want to fix before going further, if for no other reason than it being important to have an independent backup of your Developer ID signing identities [1]. Here’s a test for you to run: Log out of that account. Log in to some other account. Make a copy of the keychain from the old account, that is, ~xyz/Library/Keychains/login.keychain-db, where xyz is the old account name. Rename it. Add it to Keychain Access on the new account (File > Add Keychain). Can you then export it from there? In fact, it’d be even better to copy it to a completely different machine! That’ll tell you whether the keychain itself is borked, or whether there’s something about your account, or indeed your machine, that’s triggering these problems. For ex

Question 1: When the digital crown is pressed during a call, a message appears on the screen stating, End Call to Continue, and the call cannot be moved to the background. As a result, it is not possible to operate other apps while on a call. Is this behavior due to the specifications of CallKit? Yes, this is how CallKit works on watchOS. Question 2: Our app stops communication when it goes into the background, but the walkie-talkie app on the Apple Watch can transition to the background by pressing the digital crown during a call, allowing it to continue receiving and playing the other party's audio while in the background. watchOS does not currently have a public API that will allow your app to do this. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Would it be possible to disable or hide the “Leave” button in the system screen? No. You can certainly file an enhancement request asking for use to provide/tweak what we show here, but the system is always going to provide some way for the user to directly stop the PushToTalk session. That's because one of the primary goals of the PushToTalk framework was providing user level control over this. I only receive the APNs push notification “type: voip-ptt“ once per active channel. My forum post here goes into this in depth, but the quick summary is that you shouldn't think of the PushToTalk framework's channel as the same thing as your apps. The PushToTalk framework's channel is simply it's connection to your app. There will ONLY ever be one of them and you should not be creating/leaving/joining that channel dynamically. You join it when your PTT session starts and you don't leave it until you session is done. Again, see my other forum post for more details on that means in practice. My app is running in the bac

The Pop-up button page in the HIG has a link to SwiftUI MenuPickerStyle along with a link to NSPopUpButton for AppKit. I'm actually not familiar with AppKit or SwiftUI (just UIKit) but hopefully that points you in the right direction.

I'd like to answer the second question first. The lldb config file can be selected by editing the Run scheme action. Specifically, use the menu bar, go to Product -> Scheme. Make sure the desired scheme is selected, and click on Edit Scheme.... In the pop up window, select the Run action from the column on the left. Then click on the Info tab. The lldbinit file can be specified through the field in the middle. Going back to the first question. Since we can explicitly specify a path to the lldbinit file, we can place it anywhere in the project. Is this sufficient to get you going? Please let us know and I will follow up. Thanks!