react-native-webrtc / react-native-webrtc/react-native-callkeep
Receiving: UnsupportedOperationException: System does not support feature android.software.telecom error on android
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Bug report
- Reproduced on:
- Android
- iOS
Description
Hey team! One of our customers is reporting that the app crashes immediately when booting our app. It looks like this is the error that they are running into. I guess their device doesn't have telephony support? It looks like a tablet so I guess that lines up. There are no workarounds, correct? Other than declaring no support for devices with no telephony support
Steps to Reproduce
Can't open the app on android tablet
Versions
- Callkeep: 4.3.8
- React Native:0.71.19
- iOS:
- Android: 14
- Phone model: Lenovo TB132FU
Logs
Exception java.lang.UnsupportedOperationException: System does not support feature android.software.telecom
at android.os.Parcel.createExceptionOrNull (Parcel.java:3023)
at android.os.Parcel.createException (Parcel.java:2995)
at android.os.Parcel.readException (Parcel.java:2978)
at android.os.Parcel.readException (Parcel.java:2920)
at com.android.internal.telecom.ITelecomService$Stub$Proxy.registerPhoneAccount (ITelecomService.java:1738)
at android.telecom.TelecomManager.registerPhoneAccount (TelecomManager.java:1503)
at io.wazo.callkeep.RNCallKeepModule.registerPhoneAccount (RNCallKeepModule.java:979)
at io.wazo.callkeep.RNCallKeepModule.registerPhoneAccount (RNCallKeepModule.java:286)
at io.wazo.callkeep.RNCallKeepModule.setup (RNCallKeepModule.java:263)
at java.lang.reflect.Method.invoke
at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372)
at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:188)
at com.facebook.jni.NativeRunnable.run
at android.os.Handler.handleCallback (Handler.java:942)
at android.os.Handler.dispatchMessage (Handler.java:99)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27)
at android.os.Looper.loopOnce (Looper.java:201)
at android.os.Looper.loop (Looper.java:288)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228)
at java.lang.Thread.run (Thread.java:1012)
Caused by android.os.RemoteException: Remote stack trace:
at com.android.server.telecom.TelecomServiceImpl.enforceTelecomFeature (TelecomServiceImpl.java:2449)
at com.android.server.telecom.TelecomServiceImpl.enforcePhoneAccountModificationForPackage (TelecomServiceImpl.java:2409)
at com.android.server.telecom.TelecomServiceImpl.-$$Nest$menforcePhoneAccountModificationForPackage
at com.android.server.telecom.TelecomServiceImpl$1.registerPhoneAccount (TelecomServiceImpl.java:564)
at com.android.internal.telecom.ITelecomService$Stub.onTransact (ITelecomService.java:857)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The crash enters RNCallKeepModule.java through setup and registerPhoneAccount on an Android 14 tablet without telecom support. Start by tracing those methods and reproducing the failure on the reported Lenovo TB132FU; done means startup no longer crashes on unsupported devices while supported-device behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100