You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the app is terminated, calling from the Android native UI such as the recents or dialpad, and selecting the app's calling account, does not seem to initialize the app and hence the CallKeepDidReceiveStartCallAction event is never triggered. When the app is in the background, everything works as expected.
Is this even possible on Android (maybe it's a permission issue?), as iOS seems to do this out of the box?
The text was updated successfully, but these errors were encountered:
When the app is terminated, calling from the Android native UI such as the recents or dialpad, and selecting the app's calling account, does not seem to initialize the app and hence the CallKeepDidReceiveStartCallAction event is never triggered. When the app is in the background, everything works as expected.
Is this even possible on Android (maybe it's a permission issue?), as iOS seems to do this out of the box?
The text was updated successfully, but these errors were encountered: