React Context Lost After Call Accept From Lock Screen In Production

[hevi08]

In production builds, the React Context is lost when the user accepts an incoming call from the lock screen and app is in killed state.

Here is how i am using this library,

• FCM Push Notification is received
• RNCallKeep is initialized and events are registered
• RNNotificationCall events are registered
• RNNotificationCall.displayNotification is called
• The app shows the incoming call UI on the lock screen
• As soon as I accept the call and unlock the screen (with a password), the app opens with a fresh state

At this point, I lose the static instance and data inside the RNCallKeep class, which contains required information for the ongoing call.

This issue does not happen if the app is launched from a killed state and the screen is already unlocked before the FCM notification is received.

If i am using only FCM, and open ongoing call screen from lock screen it opens without losing state.

Also, is there anyway i can test lock screen and app killed state behaviour in dev mode ?

[hevi08]

In the same scenario, if I use the default UI (without passing mainComponent), it works.

[linhvovan29546]

Hi @hevi08 Since your report covers multiple issues, could you help me understand which one is most critical?
From the description, this seems like a Js implementation challenge, let me know if you believe it's related to this library specifically or Could you specify the exact problem you need resolved?

[hevi08]

After receiving the FCM, registering RNCallKeep Events and then call RNNotificationCall.displayNotification() on showIncomingCallUi callkeep event.

Scenarios

App State (Background / Foreground / Killed)	Device State (Locked / Unlocked)	UI Type	mainComponent Passed	Behavior	Working
Any	Any	Default (Library UI)	❌ No	Incoming Call shown, state preserved	✅ Yes
Any	Unlocked	Custom	✅ Yes	Incoming Call shown, state preserved	✅ Yes
Background	Locked	Custom	✅ Yes	Incoming Call shown, state preserved	✅ Yes
Killed	Locked (with password as none)	Custom	✅ Yes	Incoming Call shown, state preserved	✅ Yes
Killed	Locked (with password as swipe, pin, fingerprint, etc.)	Custom	✅ Yes	Incoming Call shown, but state is lost	❌ No

Fifth scenario is the issue, when the call is accepted, the app launches in a fresh state — all previous state, including RNCallKeep registered events and static values like this are lost.

I hope this clarifies the issue.

[linhvovan29546]

Thank you for your patience, sorry for the delayed reply.

Also, is there anyway i can test lock screen and app killed state behaviour in dev mode ?

I remember that I was still testing in dev mode. After receiving a notification, the app was triggered to run in the background (headless mode).

Fifth scenario is the issue, when the call is accepted, the app launches in a fresh state — all previous state, including RNCallKeep registered events and static values like this are lost.

Unfortunately, I'm not working on the project that uses incoming calls, so I can't help you with this. Does this bug occur both when you pass a mainComponent (custom UI) and when you don't use mainComponent? This might be related to a setting in the manifest.

[hevi08]

Does this bug occur both when you pass a mainComponent (custom UI) and when you don't use mainComponent?

Only when mainComponent is passed as i mentioned in above table.