Skip to content

[IOS] Fix the issue where a call does not open the app when the device is in a locked or killed state. - #670

Closed
MingHieu wants to merge 1 commit into
react-native-webrtc:masterfrom
MingHieu:fix-start-call
Closed

MingHieu wants to merge 1 commit into
react-native-webrtc:masterfrom
MingHieu:fix-start-call

Conversation

@MingHieu

Copy link
Copy Markdown

No description provided.

@manuquentin

Copy link
Copy Markdown
Contributor

Thanks @MingHieu for the PR.

If the bridge is not yet listening to events, have you tried to use the didLoadWithEvents listener to get non fired events ?

@MingHieu

Copy link
Copy Markdown
Author

@manuquentin When the app in kill state and screen is locked, I swipe to answer and my app not even start until I press the icon on the native call screen. I met this issue long time ago and not recheck yet.

@saif-o99

Copy link
Copy Markdown

i believe this is the native behaviour of the IOS

@sboily

sboily commented Oct 17, 2026

Copy link
Copy Markdown
Member

Thanks, and sorry for the delay. This handler was removed on purpose in 1455d42. On master, an event received before JS is listening is kept and delivered through didLoadWithEvents / getInitialEvents, and #877 (merged yesterday) fixed the case where events received in the AppDelegate before the module was initialized were lost. A fixed 5-second delay would also slow down every cold start from Recents. Closing; if you still see the problem on master with getInitialEvents, please open an issue with the steps.

@sboily sboily closed this Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants