[Bug]: InCallService PhoneAccountHandle is null, fatal crash

[TheGoodDoctor154]

Checklist

• I have read the application docs, searched existing issues and discussions and this is not a duplicate
• I am using the latest version of the project
• I am reporting an issue with ShizuCallRecorder itself, NOT an issue about Shizuku or another app
• I have attached or pasted the required log files below (or explained why they are unavailable)

ShizuCallRecorder Version

1.3.3

Shizuku Version

Shizuku next 14.0.14

Android Version

Android 16

The model of your device

Samsung s24 ultra one ui 8.5

Explain the bug

There was no error while using the app.
I just ran logfox for few hours and forgot about it.
When I saw there were two crash logs.
I don't know what it shows. You can see if it's of any significance.
Thanks

Steps to Reproduce

Ran logfox on my device

Logs

crash-com-kitsumed-shizucallrecorder-07_10-19-43-46_618.log
crash-com-kitsumed-shizucallrecorder-07_10-13-26-24_904.log

[kitsumed]

Yes, this is indeed a bug. According to Android docs, PhoneAccountHandle.getComponentName should never return null... I guess we will have to add a safety check.

This is weird because I remember an older Android version (I think 13?) had a similar bug, but it was constant, and was fixed in followup versions. This time it's Android 16 so it's weird, I never got this issue and clearly this is not wide-spread since you're the first one to report this.

Will try to fix this for the v2.0.0 release.

Do you know when/what you are doing before this crash occur?

[kitsumed]

@TheGoodDoctor154 I did more search, this is not your first time around with this type of bug (PhoneAccountHandle = null) we previously fixed a bug related to your dual-sim usage #81.

I would like to get the app runtime logs too so I can see if this is another one of thoses error that only happen when the call state is in a specific state. Last time it only occured when the state was Call.STATE_SELECT_PHONE_ACCOUNT which is the UI that ask you which SIM card you wish to use, so we fixed that.

This time I don't know what's the problem. I only know that it's null again.

[TheGoodDoctor154]

I actually don't know what I was doing. As I said I was just gettings some logs for some other app and started recordingbwith logfox app. After few hours I remembered that I started the recording and I went inside the app and in crashes segment I saw there are two crashes although I saw no errors on my screen during any calls.
How can I help?

[kitsumed]

Can you enable log recording inside ShizuCallRecorder and export the log file when the error occur?