react-native-webrtc / react-native-callkeep

iOS CallKit framework and Android ConnectionService for React Native
ISC License
899 stars 438 forks source link

Map already consumed exception (VoiceBroadcastReceiver.onReceive) #643

Open KolissnikBogdan opened 1 year ago

KolissnikBogdan commented 1 year ago

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?

Versions

- Callkeep: ^4.3.3
- React Native: 0.63.5
- iOS: -

Here are some screenshots from google play console:
image_2022_12_14T13_40_05_482Z image_2022_12_14T13_40_36_648Z

nagyszili commented 1 year ago

I experienced this issue too in self managed mode when I wanted to display an Incoming call from background and the setup was not called before

KolissnikBogdan commented 1 year ago

@nagyszili hmm, are you setting the settings on the native side?

nagyszili commented 1 year ago

What do you mean? You mean this? I did not setted anything native side, I'm only using a native incoming call screen. I'm using with expo and expo config plugin

wilmxre commented 1 year ago

@KolissnikBogdan did you find a fix for this?

SuperBesse commented 10 months ago

Fix available on 4.3.4 => https://github.com/react-native-webrtc/react-native-callkeep/commit/6204cc01ec47d521599d9eabc6055d2ef369253e