Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bridge is flasky on iOS

See original GitHub issue

I set up the CallDetector in componentDidMount on one of my screens, pretty much in the same way that it was set on the example:

https://github.com/priteshrnandgaonkar/react-native-call-detection/blob/7c47b4d2c3510377e890e7b825f8c59c1f42dfc8/CallDetectionExample/src/HomeComponent.js#L29

However, from time to time I receive the following error (it doesn’t happens every time, but frequently) after ending a call:

bridge is not set. 
This is probably because you've explicitly synthesized the bridge in RCTCallDetection, 
even though it's inherited from RCTEventEmitter.

Could this be related to memory leak? Has anyone had this problem?

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:5 (1 by maintainers)

Top GitHub Comments

2reactions

dowatugkinscommented, Jul 31, 2019

@julioxavierr @soledaddiez If you could pull my branch and test to see if it fixes your issue, that would be great. We also ran into this issue, and noticing that this repo uses the deprecated API CallTelephony I updated the iOS side to use the new CallKit API instead. So far I haven’t seen any crashes and get the same events as expected when expected.

0reactions

priteshrnandgaonkarcommented, Apr 16, 2020

Closing it as its a stale issue