Element IOS app Crash issue

[Siam-1998]

Steps to reproduce

1.App crashes when we make audio and video calls

Outcome

1.App crashes when we make audio and video calls

Your phone model

iphone12

Operating system version

16.4.1

Application version

1.10.11

Homeserver

Synapse 1.81

Will you send logs?

Yes

[Velin92]

Hi!
Could you please provide us the logs?
Thanks.

[muczek]

I've also noticed similar or maybe same problem. In my case, from user point of view, only pressing green button in chat on top toolbar to make voice call is enough to trigger error described above. Unfortunately it is non deterministic and to be honest it is hard for me to reproduce.
I am pretty sure the source of the problem is related to JitsiMeetSDK update (method JMCallKitEmitter provider:didActivateAudioSession: is the last one on stacktrace). Maybe there is a problem with methods responsible for adding/removing JitsiCallKitProxy listeners (methods: start(), stop() in class CallPresenter).

[Siam-1998]

Thanks For Replying
I am not using jitsi service for for calling, i am using coturn service

[alexander-potemkin]

it seems like we encounter the same issue - it's like 3-4 different phones. How I can get logs from iOS app crashing? Don't use have Sentry integrated to catch that?

[alexander-potemkin]

Thanks For Replying
I am not using jitsi service for for calling, i am using coturn service

@Siam-1998 , could you please, share how did you do that?

[Velin92]

it seems like we encounter the same issue - it's like 3-4 different phones. How I can get logs from iOS app crashing? Don't use have Sentry integrated to catch that?

Yes, but would be also very helpful to provide us also a rageshake report, and provide us here the name of the report so we can look at the full logs of the application (both the crash logs and the logs before the crash) to get a better insight of what state could have caused it.

[alexander-potemkin]

Yes, but would be also very helpful to provide us also a rageshake report, and provide us here the name of the report so we can look at the full logs of the application (both the crash logs and the logs before the crash) to get a better insight of what state could have caused it.

My problem with rageshake reports is that they are quite informative... I understand - it's a benefit from the debugging perspective but that is also a trouble from the privacy perspective...

Is there anything else I could do to assist you with troubleshooting, @Velin92 ?

[toshanmugaraj]

yes randomly crashes.

[alexander-potemkin]

@Velin92 , I've got it on my device as well. I tried to establish direct call with the person and the app just crashed a few times when I tried to do that. My workaround was that I asked the guy to call me and it started working.

I understand such cases are not easy to handle, but I would expect you shall be able to get exception stack from your crash catching system if I provide you my device id or other information.

I'm pretty much sure there are other things to do to handle that. Please, correct me if I'm wrong, but app crashes shall be handled as a priority.