Can we expect an answer from Apple on this topic?
We are facing the same issue with our P2P messaging application.
Shall we use the undocumented 'com.apple.developer.pushkit.unrestricted-voip' that some applications seem to use (WhatsApp, Signal, Telegram)?
ciceron1
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
We are facing the same issue with Twinme messaging application and I've not had any response to my question
https://developer.apple.com/forums/thread/129401
You cannot tell your users to re-install the application to fix this bad behaviour once you have fixed a crash bug on your side.
Same issue for me today (March 3rd, 2023) and the Apple server status looked good. I had the issue on several projects.
Restarting Xcode solved the problem for me.
It is unbelievable and very sad that a 400Mds company is providing and forcing us to use such buggy environment....
As usual, Apple documentation is unclear about that. It should be called after you have called CallKit, it after reportNewIncomingCallWithUUID is done.
It is still not clear for me how much time we have to call that completion handler.
The version without completion handler must terminated within 30s (and this is again, not very well documented...)
I've just hit the same issue after switching to Xcode 14.3. Linking our iOS application with WebRTC C++ static library now produces 2500 warnings. I guess this is the dsymutil that has problems. Building for arm64 and WebRTC C++ library targets arm64 also.