Popping Sound

Hm. That sounds like a decent solution, but that hasn't been my experience in the past. I'll have to check whether that's what's happening.

is an xcframework an appropriate approach for this? It sounds like a Swift Package would be a better idea. You could include the xcframework and define any external dependencies, as described here.

We're building a taxi driver app. Our goal is simple: Play a notification sound when a new ride request arrives — even if the iPhone is connected to CarPlay. We use Firebase push with sound: default and interruption-level: time-sensitive. The app requests .carPlay and uses a category with .allowInCarPlay. Everything works when CarPlay is disconnected — we get sound and banner. But when connected to CarPlay: the push is delivered silently, no sound is played (even on the phone), Siri Announce is enabled, but nothing is spoken. Questions: Is notification sound blocked when CarPlay is active, unless the app has CarPlay entitlement? Is Siri Announce the only way to notify the driver audibly in this case? Would getting a CarPlay entitlement (e.g. CarPlay.communication) fix this without building a full CarPlay UI? Thanks — all we need is a reliable sound alert when a new ride comes in.

if using the in-house app, there may be crashes in the new iOS 18.3 and later versions This sounds like it could be a known issue affecting some versions of iOS 18, and is specific to in-house or enterprise distribution. You'll want to read the details on this other thread, which includes steps you can take for resolution. If that turns out not to be the case, then as darkpaw says, we'll need more information from you to give us a starting point. Since you're highlighting an enterprise app, I suggest you do so by filing a bug report with a sysdiagnose attached. You can post the FB number of the report here, and we can take a look from there. — Ed Ford,  DTS Engineer

Thanks for confirming this is a custom intent. In that case, checking for Siri authorization at the API level isn't required. The system may ask people to confirm their intention when using your intent through Sri for the first time, but that's not something you need to worry about at the API level. I didn't find the api to check if Siri enabled or not at user's end(like if Siri is enabled on their phone), is it because this information is not shared with the app? A custom SiriKit intent is surfaced in multiple places throughout the system experience, such as Spotlight, certain system provided widgets that suggest relevant actions to the user based on their use patterns, and more. Checking for Siri authorization isn't really useful, because that's a binary answer for only one place of many where your intent could run. Thus, the APIs are set up so that your app doesn't need to reason about all of the numerous situations. I want to come back to your original premise: My team wants to improve the user experience

My app has a network extension, and I've noticed each phone having their connectivity interupted by calls on the push provider, calling stop with the noNetworkAvailable reason. The point of confusion is that each phone seems to get it's interruption at different times. For example one will get an interuption at 1:00, while the others is fine, while at 3:00 another will get an interuption, while the others are fine. What were the phones physically doing at the time the interruption occurred? The most common reason this occurs is simply that the device moved out of WiFi coverage. A few notes on that point: Providing good WiFi coverage over a large area under real world conditions is sufficiently difficult that unless a large scale network has been well surveyed and professionally maintained, significant dead zones are all be guaranteed. In my experience, users reports of their active (I was in range so it should have worked) are completely unreliable. Network configuration is more complicated and error prone th