react-native-webrtc / react-native-webrtc/react-native-callkeep
Map already consumed exception (VoiceBroadcastReceiver.onReceive)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Hello everyone) After updating to the latest version of the program, there were a lot of crash reports with the following error:
Exception com.facebook.react.bridge.ObjectAlreadyConsumedException: Map already consumed
at com.facebook.react.bridge.WritableNativeMap.putString
at io.wazo.callkeep.RNCallKeepModule$VoiceBroadcastReceiver.onReceive (RNCallKeepModule.java:1158)
at androidx.localbroadcastmanager.content.LocalBroadcastManager.executePendingBroadcasts (LocalBroadcastManager.java:313)
at androidx.localbroadcastmanager.content.LocalBroadcastManager$1.handleMessage (LocalBroadcastManager.java:121)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loopOnce (Looper.java:233)
at android.os.Looper.loop (Looper.java:344)
at android.app.ActivityThread.main (ActivityThread.java:8191)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:584)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1034)
Maybe someone also faced this problem?
- Reproduced on:
- Android
- iOS
Versions
- Callkeep: ^4.3.3
- React Native: 0.63.5
- iOS: -
Here are some screenshots from google play console:


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
Start at RNCallKeepModule.java:1158 in VoiceBroadcastReceiver.onReceive and inspect the WritableNativeMap usage shown in the Android stack trace. Reproduce the reported Android broadcast path with CallKeep 4.3.3 and React Native 0.63.5, then verify that the crash no longer occurs and add or update a regression test if the repository provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100