@darkpaw Thanks for the reply, but I face this issue in my code and I can replicate it in the Apple CallKit demo. So I ask Apple dev here for suggestions and when this issue will be fixed. As I know, the iOS 17 is ok and other iPhone without dynamic island is ok.

Hey Apple, I tested with iOS 18.4, and all works well for now. So you guys fixed it secretly again?

Any update? @apple dev

Any updates for this? @apple

and how about the "ActivePrewarm" logic, will it impact this?

Thanks for your info, very helpful. One point to be clear: How to define the debug case: "for example if you are debugging your app at the time via Xcode". Cable conntected? Open console app? Open Xcode connect device. I tested my App store build and installed the APNs profile in my device. (iPhone 12 pro max, iOS18.3) Then I can see the app has been waken up from manual killed status from this method. func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool and the launchOptions like: Optional([__C.UIApplicationLaunchOptionsKey(_rawValue: UIApplicationLaunchOptionsRemoteNotificationKey): { action = StopRing; aps = { "content-available" = 1; }; event = "/restapi/v1.0/account/xxxx/extension/xxxx/stop-ring"; from = 101; fromName = Lxx; serverId = "10.74.13.129.TAM"; telephonySessionId = "s-98cdf84c5e474a80a671895c750a293a"; timestamp = "2021-04-23T09:14:11.971Z"; to = 101; }])

@Engineer The WIFI works well while the VoIP push doesn't work because my app works for other features, like sending/receiving messages via REST API. Just the VoIP push failed. btw, you said "restart the iPad", is it means the "force-restart"? https://support.apple.com/en-sg/guide/iphone/iph8903c3ee6/ios

yes, I'm doing so. but in the case I post above: When BT (Airpods pro 2) DISCONNECTTED: it will print like below when the route change notification comes, this is wrong. should not contains the "BluetoothHFP" at this time. So @Engineer you can have demo based on my code. availableInputs=[__C.AVAudioSessionPort(_rawValue: MicrophoneBuiltIn), __C.AVAudioSessionPort(_rawValue: BluetoothHFP)], currentRouteInputs=[], currentRouteOutputs=[__C.AVAudioSessionPort(_rawValue: Speaker)]

Thanks. @Engineer , I will check your info. But for now, my requirement is to create a button that can indicate the audio route state, eg: If no BT is connected, just a built-in and the speaker, Show a button with 2 states: normal(for build-in) and selected(Speaker). If has BT connected, tap the button will show the system "AVRoutePickerView" for user to choose a route. but now, I can't get the correct state when "user choose speaker when BT connected", at this time, when user tap the button, I need to show the "AVRoutePickerView", but the current route is speaker, I don't know if the BT is connected. Hope you can understand my requirements. thanks.

We understand the importance of providing a focused sample project to reproduce the issue. However, this appears to be a rare and intermittent case, and we have not been able to reproduce it consistently in our testing environment. Here are the reproduction steps provided by the affected user: Make a VoIP call using our app. Switch the audio route from the built-in microphone to AirPods Pro (model: A2084, version: 6F21) during the call. Could you please provide further insight into the above questions?

I have the same case reported by a user. The CallKit screen covered our app screen, so no way to operate on our app unless switch it to the foreground manually. But I can't reproduce it locally with same device and iOS version ( iPhone 15 Pro; iOS/18.0.1). So @Engineer, any updates now? TIA.

First, you must set the 'apns-priority' as '5' when you send a silent push. You can try it again. It actually can wake my app from "Killed" to "Background", but after that, you still can't find it in the "Recent apps" list. I just checked that it actually runs from the Console app log.

Hey Apple! You fixed this in iOS16.5? right? btw: @revanth Please check your data with iOS16.5.

@svent Sorry, I upload the wrong crash file. Here is the correct one. Please check. 2023-05-05_11-33-23.8089_-0700-606e5583676c23fb93e3ddb067aee154b5974ddb.crash