Ricardo Corrie
Ricardo Corrie
@divyesh-puri I am seeing the same issue, but only on development builds. Release builds work fine. Is this also the case for you? I'm thinking it might have to do...
I am also experiencing this issue. I am running the latest CallKeep release and `didLoadWithEvents` does not fire at all for me.
@Romick2005 I will try this tomorrow, thank you
I found my issue. `didLoadWithEvents` is giving different event names than the eventListeners expect. For example, `didDisplayIncomingCall` is named `RNCallKeepDidDisplayIncomingCall` when it comes in via `didLoadWithEvents`. I'm not sure if...
@Romick2005 In the main repo. I haven't tested your fork. For example, when you add an event listener for incoming calls, you set it up with the event name `didDisplayIncomingCall`...
My initial assumption was incorrect. I thought `didLoadWithEvents` was not being emitted because I was looking for `didDisplayIncomingCall` instead of `RNCallKeepDidDisplayIncomingCall`
I submitted a PR with a fix to this issue @nagyszili can you please test?
I've experienced this after reloading the app (reloading in metro bundler, not killing the app).
UPDATE: This happens when the client is connected to a VPN. Any idea what's going on @datso ?
I am experiencing this on Android Lollipop (API 21 and 22). On my newer devices it works well. It seems like the callback passed to the `start` method is never...