Open Radar

 
Area:
Something not on this list

Summary:
When a CallKit-enabled call fails, the system shows a native UI with two buttons: Cancel and Call Back. However, tapping Call Back has no effect at all. I was expecting that this button will send a new perform:CXStartCallAction to my CXProviderDelegate, but I also tried listening to application:continueUserActivity, whithout any luck. 

The same behaviour can be observed in the Speakerbox example app: siumulate an incoming call, then in the perform:CXAnswerCallAction I set a timer to force the call to fail after 5 seconds. The 'Call Failed' native UI shows, however Call Back button does nothing.

We attach a file with the device logs at the moment of tapping the 'Call Back' button

Steps to Reproduce:
1. Start a CallKit-enabled call.
2. The call fails for any reason (reported to CallKit via reportCallWithUUID(uuid, endedAtDate:nil, reason: .Failed)).
3. The Call Failed native UI shows (see attachment).
4. Tapping 'Call Back' has no effect at all on the app (no CXProviderDelegate callbacks, or NSUserActivity continuations).

Expected Results:
Tapping 'Call Back' button should communicate with the app to start a new call (probably via CXProviderDelegate performStartCallAction).

Actual Results:
Nothing happens. The screen is not dismissed and the app doesn't receive any CXProviderDelegate or AppDelegate callback.

Version:
iOS 10 Beta 4

Notes:


Configuration:
iPhone 5S