Failed to activate audio session in iOS native app

3,346 views
Skip to first unread message

Gustavo García

unread,
Apr 25, 2018, 7:35:33 AM4/25/18
to discuss-webrtc
Hi all,

Reviewing the metrics we have for client errors in production I see there is a relevant amount of users getting error 561017449 when trying to activate or configure the AVAudioSession.  These are the errors:

Failed to setActive:1. Error: The operation couldn’t be completed. (OSStatus error 561017449.)
Failed to set WebRTC audio configuration: The operation couldn’t be completed. (OSStatus error 561017449.)"

Error 561017449 is supposed to be insufficientPriority but I don't know what can be the reason/scenario why this could be happening.   I was able to reproduce it only if I establish a Facetime call first and I start a WebRTC call while the FT call is still in progress, but I doubt that is a common scenario in the real world.

I've also seen similar issues in the past when combining CallKit but I know in most of these cases CallKit was not involved.

Anybody else seeing these issues or any suggestion?

Jiawei Ou

unread,
Apr 25, 2018, 10:21:47 AM4/25/18
to discuss...@googlegroups.com
Insufficient priority can also be caused by the user in a pstn call receiving an incoming webrtc call.

CallKit usually generate some errors like invalid provision.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAPx8CAaAtW9KBDHrYi20z3JGxcz%3DJc%3Df0qQr76DXh57vA4cF3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Sent from a nondescript phone which won't pay me for advertising it. Excuse brevity.

Zeke Chin

unread,
Apr 25, 2018, 12:27:58 PM4/25/18
to discuss-webrtc
Outside of a ongoing phone call or system audio event, insufficient priority is usually transient (sometimes it takes a while after PSTN / system audio event is over before you can actually activate).

You can implement some retry logic around that specific error and it should eventually succeed if you're in the foreground.

On Wed, Apr 25, 2018 at 4:21 PM, Jiawei Ou <jiaw...@gmail.com> wrote:
Insufficient priority can also be caused by the user in a pstn call receiving an incoming webrtc call.

CallKit usually generate some errors like invalid provision.
On Wed, Apr 25, 2018 at 4:35 AM Gustavo García <gust...@gmail.com> wrote:
Hi all,

Reviewing the metrics we have for client errors in production I see there is a relevant amount of users getting error 561017449 when trying to activate or configure the AVAudioSession.  These are the errors:

Failed to setActive:1. Error: The operation couldn’t be completed. (OSStatus error 561017449.)
Failed to set WebRTC audio configuration: The operation couldn’t be completed. (OSStatus error 561017449.)"

Error 561017449 is supposed to be insufficientPriority but I don't know what can be the reason/scenario why this could be happening.   I was able to reproduce it only if I establish a Facetime call first and I start a WebRTC call while the FT call is still in progress, but I doubt that is a common scenario in the real world.

I've also seen similar issues in the past when combining CallKit but I know in most of these cases CallKit was not involved.

Anybody else seeing these issues or any suggestion?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
--
Sent from a nondescript phone which won't pay me for advertising it. Excuse brevity.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAA--a%2B1pN9ygecPgRR41HQ0c%2BZcmjD89AO9FCC5NBVJczGMFRw%40mail.gmail.com.

Gustavo García

unread,
Apr 25, 2018, 4:18:52 PM4/25/18
to discuss...@googlegroups.com
Thank you very much for the answers.   The AVAudioSession in WebRTC is only activated after accepting the call (when applying the SDPs) and I think few users will accept the incoming WebRTC call while in a PSTN call.   Because of that and the fact that I've seen the logs of some specific user reports where there was definitely no PSTN call involved I think there is some other problem here.

We have implemented the retry logic although we still don't have numbers to see how effective it is.   Just wondering if anybody else is seeing this issue in the wild so that we can try to find a fix to put inside libwebrtc's code.


El mié., 25 abr. 2018 a las 18:27, Zeke Chin (<tkc...@webrtc.org>) escribió:
Outside of a ongoing phone call or system audio event, insufficient priority is usually transient (sometimes it takes a while after PSTN / system audio event is over before you can actually activate).

You can implement some retry logic around that specific error and it should eventually succeed if you're in the foreground.
On Wed, Apr 25, 2018 at 4:21 PM, Jiawei Ou <jiaw...@gmail.com> wrote:
Insufficient priority can also be caused by the user in a pstn call receiving an incoming webrtc call.

CallKit usually generate some errors like invalid provision.
On Wed, Apr 25, 2018 at 4:35 AM Gustavo García <gust...@gmail.com> wrote:
Hi all,

Reviewing the metrics we have for client errors in production I see there is a relevant amount of users getting error 561017449 when trying to activate or configure the AVAudioSession.  These are the errors:

Failed to setActive:1. Error: The operation couldn’t be completed. (OSStatus error 561017449.)
Failed to set WebRTC audio configuration: The operation couldn’t be completed. (OSStatus error 561017449.)"

Error 561017449 is supposed to be insufficientPriority but I don't know what can be the reason/scenario why this could be happening.   I was able to reproduce it only if I establish a Facetime call first and I start a WebRTC call while the FT call is still in progress, but I doubt that is a common scenario in the real world.

I've also seen similar issues in the past when combining CallKit but I know in most of these cases CallKit was not involved.

Anybody else seeing these issues or any suggestion?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
--
Sent from a nondescript phone which won't pay me for advertising it. Excuse brevity.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAA--a%2B1pN9ygecPgRR41HQ0c%2BZcmjD89AO9FCC5NBVJczGMFRw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAB1Ysukv1_AkuBW8%3DOJxznb27ppCspRq%2B14Tgp7r%2B%2BEus6qYNQ%40mail.gmail.com.

Piyush Tank

unread,
Dec 3, 2019, 11:19:47 AM12/3/19
to discuss-webrtc
Hi Gustavo,

Did you come to any resolution on this? We just observed this issue when CallKit is in use (no PSTN call involved).

Piyush

On Wednesday, April 25, 2018 at 1:18:52 PM UTC-7, Gustavo García wrote:
Thank you very much for the answers.   The AVAudioSession in WebRTC is only activated after accepting the call (when applying the SDPs) and I think few users will accept the incoming WebRTC call while in a PSTN call.   Because of that and the fact that I've seen the logs of some specific user reports where there was definitely no PSTN call involved I think there is some other problem here.

We have implemented the retry logic although we still don't have numbers to see how effective it is.   Just wondering if anybody else is seeing this issue in the wild so that we can try to find a fix to put inside libwebrtc's code.


El mié., 25 abr. 2018 a las 18:27, Zeke Chin (<tkc...@webrtc.org>) escribió:
Outside of a ongoing phone call or system audio event, insufficient priority is usually transient (sometimes it takes a while after PSTN / system audio event is over before you can actually activate).

You can implement some retry logic around that specific error and it should eventually succeed if you're in the foreground.
On Wed, Apr 25, 2018 at 4:21 PM, Jiawei Ou <jiaw...@gmail.com> wrote:
Insufficient priority can also be caused by the user in a pstn call receiving an incoming webrtc call.

CallKit usually generate some errors like invalid provision.
On Wed, Apr 25, 2018 at 4:35 AM Gustavo García <gust...@gmail.com> wrote:
Hi all,

Reviewing the metrics we have for client errors in production I see there is a relevant amount of users getting error 561017449 when trying to activate or configure the AVAudioSession.  These are the errors:

Failed to setActive:1. Error: The operation couldn’t be completed. (OSStatus error 561017449.)
Failed to set WebRTC audio configuration: The operation couldn’t be completed. (OSStatus error 561017449.)"

Error 561017449 is supposed to be insufficientPriority but I don't know what can be the reason/scenario why this could be happening.   I was able to reproduce it only if I establish a Facetime call first and I start a WebRTC call while the FT call is still in progress, but I doubt that is a common scenario in the real world.

I've also seen similar issues in the past when combining CallKit but I know in most of these cases CallKit was not involved.

Anybody else seeing these issues or any suggestion?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss...@googlegroups.com.
--
Sent from a nondescript phone which won't pay me for advertising it. Excuse brevity.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss...@googlegroups.com.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages