I am trying to make a short video for an app preview on the app store page. My iOS app uses the CallKit feature, and I would like to screen record the incoming call to show how the app works. However, the screen recording stops when there is an incoming call (which is invoked by CallKit), thus I cannot fully record the usage end-to-end. Not to mention you can't start screen recording while there is an active call. Is there a way to override this? Or is there a common way to screen record CallKit usage?

I am building a WebRTC based app that enables peer-to-peer voice calls between two users. The app works flawlessly when the device is connected to WI-FI, but I am encountering low level TCP related network issues when one of the devices is connected to the internet with 4G. This happens when two devices are exchanging WebRTC candidate informations. Once the problem occurs, the device produces errors like below every few seconds. 2021-02-22 10:31:52.952548-0800 App[9718:624872] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received 2021-02-22 10:31:52.953908-0800 App[9718:624872] Connection 3: encountered error(1:53) 2021-02-22 10:31:56.371279-0800 App[9718:625253] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received 2021-02-22 10:31:58.067480-0800 App[9718:625253] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received 2021-02-22 10:32:01.330340-0800 App[9718:625340] [tcp] nw_proto_tcp_route_init [C3:2] no mtu received The thing is that once the device encounters the above error, the device isn't able to receive PushKit notification (or so any kinds of 'push' from the server, including WebSocket push), while the device can still initiate HTTP calls. It is as if the device's some part of the network connection goes into a "stall" or "locked-in" state where it starts operating abnormally. This problem resets as soon as I change the internet connection back to WI-FI, but comes back when I switch back to 4G/LTE. The above error statement seems to be low-level network error statements, and I have no idea what I can do to diagnose the problem. Are there tools in macOS that I can use to analyze what is going on under the hood in an iOS device? Of course, I want to avoid publishing my app if it works only with a WI-FI connection, and not with 4G/5G, so this is a blocker for me. I have submitted feedback to Apple using Feedback Assistance, but I have not received a response from any one of my previous submissions, so I am a bit hopeless here and decided to ask to dev community.

I have an app that relies on features from iOS 14. However, I noticed that Sign In With Apple is not working in Simulator. I have tried with Tester iCloud account as well as real account, but they both hangs after typing the password. It appears that Sign in with Apple works in iOS 13 simulator, but I cannot use it as my app requires features from iOS 14. This forces debugging session to run only on real devices, and not on simulators, which increases development times unnecessarily. Not to mention, app reviewers may reject app submissions (I heard) due to this issue. Is there a way to get around this issue?