Open mudassir-iqbal opened 2 months ago
I can confirm this happen to our app as well!
we are struggling to reproduce the issue, do you have any information on what action are occurring leading up to the crash?
We have a fix for it in the next release but without a means of reproducing the issue we can not verify. Please let us know if it resolves your issues.
We can’t reproduce this issue on our end, but it’s affecting our customers, and crashes are being reported in Firebase Crashlytics.
Hey @mudassir-iqbal the fix is merged to main
and we plan to cut a release this week. Thanks for your patience, we'll let you know when the next version is available. However, @afalls-twilio is correct in that we are unable to reproduce the issue. Please keep informed if you still encounter the issue. Thanks for helping us make the SDK better for everyone!
Thanks for the update! I appreciate the hard work and will keep an eye out for any further issues.
Issue
In Android users occasionally experience crashes or are unable to make calls. The issue does not affect all users and seems to occur intermittently. W've tried to reproduce this locally but not luck. Mostly users are Samsung user who reported this issue.
Pre-submission Checklist
Description
Reproduction Steps
As I mention we are unable to reproduce this locally, this happen only in release builds and reported by users.
Expected Behavior
The application should allow users to initiate calls without crashing.
Actual Behavior
Some users encounter crashes or are unable to make calls. The crash logs typically include a NullPointerException related to a null Intent in the VoiceService.
Reproduction Frequency
This issue has 19 crash events affecting 5 users
in last 7 days. All Samsung devices.Software and Device Information
Additional Context
Here is my
callService.ts