“Popping Sound”

First off, a clarification here: When the phone is locked, then WhatsApp routes calls through Apple’s native CallKit. When unlocked, pressing accept essentially redirects to WhatsApp, and then WhatsApp handles the call from there. Are you sure this isn't the standard CallKit flow? Have you tested this with Speakerbox? It's possible I'm misunderstanding, but what you're describing sounds like how CallKit works by default. More specifically, accepting a call on an unlocked device opens the target app (as well as starting the call), and most apps present their own call UI when this open happens. Keep in mind that you can't actually implement a good call experience without using CallKit. For example, without CallKit, any other incoming call from any other app will immediately interrupt your call, effectively hanging up your current call. Note that this is not a theoretical problem but is in fact the primary developer complaint that led us to create CallKit. The problem is that if the phone has been recen

[quote='856443022, DTS Engineer, /thread/797469?answerId=856443022#856443022'] No, I'm talking about withoutImplicitStartAccessing. We explicitly say it does not apply to security-scoped bookmarks: [/quote] This option causes an implicit call to startAccessingSecurityScopedResource() on the returned URL when it’s ready to use the resource. The way this is written makes it sound like there will be a call to startAccessingSecurityScopedResource somewhere, so that a subsequent pair of explicit startAccessingSecurityScopedResource and stopAccessingSecurityScopedResource will still leave access at 1, leaking kernel resources. It his not the case? Is this consistent across macOS and iOS? This option isn’t applicable to security-scoped bookmarks. The documentation phrasing isn't clear about whether it's talking about NSURLBookmarkResolutionWithSecurityScope specifically (which is only available on macOS), or if it also applies to iOS (where all bookmarks are security scoped AFAIU from your earlier messages)

Sounds like this could be related to this bug here? https://developer.apple.com/forums/thread/805606?page=1#866853022

Are read-only filesystems currently supported by FSKit? I think the tricky part here is what support here actually means. Let me start by what this actually does: pass the -r or -o rdonly options to the mount(8) command. Passing that to mount should mean that the VFS layer itself is prevented from writing to the device. In FSKit terms, that means FSBlockDeviceResource.writable should be false and that all write methods should fail. If either of those behave differently, then that's a HUGE bug that we'd need to fix ASAP. However, the confusing point here is that mounting a volume readonly doesn't necessarily define/change how the file system presents itself to the higher level system. That is, strictly speaking, nothing prevents a volume being mounted readonly... but that file system itself allowing itself to be fully modifiable. That might sound a bit strange, but as a concrete example, you could implement a resettable file system by using the on-disk file system as the starting structure, routing al

This sounds like a possible regression. Can you file a feedback using Feedback Assistant and attach a sample project that reproduces the issue? Once you do, reply with the Feedback ID

This sounds like a possible framework issue. Can you file a feedback through Feedback Assistant and attach a sample project that reproduces the issue? Once you do, reply with the Feedback ID.

So the default sounds plays over a minute on loop, while my sounds stop after 27-ish (less than 30). I waited another minute to see if my sound would be repeated but nope. I plan to put the app on github as open sourced soon, does that count as test project?

How do we programmatically ensure that these notification tones are automatically and reliably routed to the connected HFP headset Take a look at Routing audio to specific devices in multidevice sessions, which covers the direct issue of audio routing. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

This post is deemed to be sensitive, and the reason is the first two words, because they sound rude when they're put next to each other: // Use the singular of cues in place of A: for A in cues { // Do a thing }

Thank you for your post. When you do not provide your file to play, and you provide the default sound with sound: AlertConfiguration.AlertSound = .default, the sound will now be the default sound.he sound looping until you stop at what time? https://developer.apple.com/documentation/alarmkit/alarmmanager/alarmconfiguration/timer(duration:attributes:stopintent:secondaryintent:sound:) Do you have the time in a focused project with the sound file you are using to share it for people to give you ideas? If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

This sounds like a regression. Have you tried verifying if the identifiers are still valid when you try to use them again? You can do this by retrieving the assets using the identifier with the fetchAssets(withLocalIdentifiers:options:) method. See the article on Fetching Assets for more details. If the identifiers are valid and you’re still encountering the issue, please file a bug report. Include a minimal reproducible sample code and share the Feedback ID here so I can pass it on to the appropriate engineering team.