-
Notifications
You must be signed in to change notification settings - Fork 75
Open
Labels
androidAffects the Android platform.Affects the Android platform.triagingInvestigating but no backlog ticket has been filed.Investigating but no backlog ticket has been filed.
Description
Issue
Getting a new crash report on Samsung phones.
Pre-submission Checklist
- I have verified that the issue occurs with the latest release and is not marked as a known issue in the CHANGELOG.md.
- I reviewed the Common Issues and open GitHub issues and verified that this report represents a potentially new issue.
- I am not sharing any Personally Identifiable Information (PII)
or sensitive account information (API keys, credentials, etc.) when reporting this issue.
Description
Getting a report of application crashing. Here is the stack trace
java.lang.RuntimeException: Unable to start service com.twiliovoicereactnative.VoiceService@fd3a48b with Intent { act=ACTION_CALL_DISCONNECT flg=0x10000000 cmp=com.xxxxxx.android/com.twiliovoicereactnative.VoiceService (has extras) }: java.lang.NullPointerException
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:5770)
at android.app.ActivityThread.-$$Nest$mhandleServiceArgs
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2728)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loopOnce(Looper.java:257)
at android.os.Looper.loop(Looper.java:342)
at android.app.ActivityThread.main(ActivityThread.java:9634)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:619)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
java.lang.NullPointerException: null
at java.util.Objects.requireNonNull(Objects.java:233)
at com.twiliovoicereactnative.VoiceService.getCallRecord(VoiceService.java:390)
at com.twiliovoicereactnative.VoiceService.onStartCommand(VoiceService.java:125)
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:5752)
at android.app.ActivityThread.-$$Nest$mhandleServiceArgs
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2728)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loopOnce(Looper.java:257)
at android.os.Looper.loop(Looper.java:342)
at android.app.ActivityThread.main(ActivityThread.java:9634)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:619)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
Reproduction Steps
Unfortunately we have not been able to reproduce this issue in a test environment
Expected Behavior
This library should not cause an application crash
Actual Behavior
Application crash
Reproduction Frequency
Unknown
Software and Device Information
Please complete the following information.
- Device: Samsung SM-F956U (AP3A.240905.015.A2)
- OS: Android 15
- React version: 19.0
- React Native version: 0.79.5
- Node version: 20.11.0
- npm or yarn version: yarn 4.9.2
- expo 53
Additional Context
Based on the stack trace it seems like it might be a call ending while the application has gone into the background.
I think ideally if whatever is happening here cannot be identified and handled correctly then at least handling the null condition more gracefully would be good.
Metadata
Metadata
Assignees
Labels
androidAffects the Android platform.Affects the Android platform.triagingInvestigating but no backlog ticket has been filed.Investigating but no backlog ticket has been filed.