Case-ID: 10075936 PLATFORM AND VERSION iOS Development environment: Xcode Xcode15, macOS macOS 14.5 Run-time configuration: iOS iOS18.0.1 DESCRIPTION OF PROBLEM Our customer experienced an one-way audio issue when switching from the built-in microphone to AirPods Pro (model: A2084, version: 6F21) during a VoIP call. The issue occurred when the customer's voice could not be heard by the other party, but the customer could hear the other party's voice. STEPS TO REPRODUCE Here are the details: After the issue occurred, subsequent VoIP calls experienced the same issue when using AirPods Pro, but the issue did not occur when using the built-in microphone. The issue could only be resolved by restarting the system, and killing the app did not work. Log and code analysis: In WebRTC, it listens for AVAudioSessionRouteChangeNotification. In the above scenario, when webrtc receives the route change notification, it will print the audio session configuration information. At this point, the input channel count was 0, which was abnormal: [Webrtc] (RTCLogging.mm:33): (audio_device_ios.mm:535 HandleValidRouteChange): RTC_OBJC_TYPE(RTCAudioSession): { category: AVAudioSessionCategoryPlayAndRecord categoryOptions: 128 mode: AVAudioSessionModeVoiceChat isActive: 1 sampleRate: 48000.00 IOBufferDuration: 0.020000 outputNumberOfChannels: 2 inputNumberOfChannels: 0 outputLatency: 0.021500 inputLatency: 0.005000 outputVolume: 0.600000 isPreferredSpeaker: 0 isCallkit: 0 } If app tries to call API, setPreferredInputNumberOfChannels at this point, it will fail with an error code of -50: setConfiguration:active:shouldSetActive:error:]): Failed to set preferred input number of channels(1): The operation couldn’t be completed. (OSStatus error -50.) Our questions: When AVAudioSession is active, the category and mode are as expected. Why is the input channel count 0? Assuming that the AVAudioSession state is abnormal at this point, why does killing the app not resolve the issue, and why does the system need to be restarted to resolve the issue? Is it possible that the category and mode of the AVAudioSession fetched by the app is currently wrong? Does it need to be reset again each time the callkit is started if the category and mode fetched are the same as the values to be set?

I have an app that was transferred from another account, but now the notifications are not working with the account's Team ID, Key ID, and .p8 file. Here are the details: On 9/14, the app was transferred to my RingCentral account. We tested the notification features, and everything worked well (both VoIP and normal push notifications). At that time, the server was still using the old Team ID, Key ID, and .p8 file configuration. On 9/24, we noticed that the notification features had stopped working. We then switched to using RingCentral's Team ID, Key ID, and .p8 file, and the notifications started working again. This raises some questions about the app transfer and notification configuration process: 3.1 After an app is transferred, do we need to immediately switch to the new account’s configuration (in this case, the RingCentral account: Team ID, Key ID, and .p8 file)? 3.2 How long does the old configuration (ld account) remain valid for notifications after an app is transferred (in this case, the Unify Office app: Team ID, Key ID, and .p8 file)? Thanks in advance for your help!

I found one crash in my organizer Crasher report, which happened on over 180 devices for 2 weeks, and it was also caught by the Firebase report, it shows it only crashed on iOS16 and iPhone devices when switching from foreground to background. But I can't replicate this crash locally and the crash stack has no info about my app class, but just some system framework. Has anyone seen a similar crash? or any suggestion to fix this from Apple dev? crashlog.crash