We have an app using CallKit since it's been introduced and had to deal with different kind of CallKit bugs and/or behaviour changes after almost every new major iOS release. But we have no ideas what to do with issue we observing on iOS17. Some users report no audio on first OUTGOING call only after app started. Subsequent calls have audio. Logs showing everything is fine - Audio Category is set, AudioUnits did setup, CallKit did activate AudioSession, and app is transferring audio frames to/from AudioUnits. But no audio. We've got reproduced this on one of devices we have and was able to fix the issue by removing paired Hearing Aid configured on the device (however the Hearing Aid was never used with this device, just config for it was iCloud synced). But we don't have confirmation from other users that there is a dependency on Hearing Aid device paired. Did anyone hit this issue as well? Any suggestions than fill Bug Report that most likely will sit forever with Apple?

WWDC 2022 announced CallKit for WatchOS 9, but didn't explain how to use it. I was able to convert SpeakerBox sample from iOS to WatchOS. The CallKit itself seems works fine, but I stuck with networking issue. I cannot understand how to stream RTP audio. I have background audio enabled. If I configure audio session for CallKit with .playAndRecord category, I cannot specify .longFormAudio policy, as it's not applicable for this category. Without .longFormAudio low lever API is denied ("Path was denied by NECP policy").

I'm trying automated signing suggested in WWDC21 session with xcodebuild and authenticationKey. I have unsigned xcarchive, .p8 key generated on portal as suggested in WWDC session, and trying to sign it with: xcodebuild -exportArchive -archivePath ./myapp.xcarchive -exportPath ./1 -exportOptionsPlist exportoptions.plist -authenticationKeyIssuerID <removed> -authenticationKeyID <removed> -authenticationKeyPath <full path to p8> -allowProvisioningUpdates However it fails, and I can see in IDEDistributionProvisioning.log the following response from Apple: Payload: {"urlEncodedQueryParams":"teamId=<removed>&filter%5BcertificateType%5D=DISTRIBUTION_MANAGED&limit=200"} 2021-09-23 10:19:23 +0000 2021-09-23 10:19:23 +0000 IDEProvisioningRepair(<removed>): 2021-09-23 10:19:23 +0000 IDEProvisioningRepair(<removed>): Received response for B50672C5-10E6-40CF-996A-097BADBD0EEF @ <https://appstoreconnect.apple.com/xcbuild/v1/certificates>. Code = 0 2021-09-23 10:19:23 +0000 2021-09-23 10:19:23 +0000 IDEProvisioningRepair(<removed>): 2021-09-23 10:19:23 +0000 IDEProvisioningRepair(<removed>): Response payload: { "errors" : [ { "id" : "8f50dfff-8ca6-442b-aa64-92f0a91730ec", "status" : "403", "code" : "FORBIDDEN_ERROR", "title" : "This request is forbidden for security reasons", "detail" : "You are not allowed to perform this operation. Please check with one of your Team Admins, or, if you need further assistance, please contact Apple Developer Program Support. https://developer.apple.com/support" } ] } If I'm trying to sign with my Dev account logged in into XCode, xcodebuil uses it instead and signing completes with no issues. Did I miss something?