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
Describe the bug
whenever I run your demo-app or I use SDK within my app, incoming call notification is not displayed when my phone is locked. I only see sound or vibration, but I don't see phone call activity on locked screen.
SDK version
1.0.17
To Reproduce
Steps to reproduce the behavior:
Log in in demo-app as Thierry on deviceA
Log in in demo-app as Tomasso on deviceB
on deviceB lock your device.
Call from Thierry to Tomasso
Vibration is heard, but device screen is still black
Expected behavior
Call Activity with incoming call should be shown on the locked screen.
Device: Any device ( I tested on 2 Samsung, one with Android 12, second with Android 9)
solution hint
I guess there is something with notification, notification intent or with activity that handles fullscreen intent. I guess that with channel - there is everything OK. Because I tested fake Notification with your channel, and it shows on locked screen. This is the body of notification I tested
Describe the bug
whenever I run your
demo-app
or I use SDK within my app, incoming call notification is not displayed when my phone is locked. I only see sound or vibration, but I don't see phone call activity on locked screen.SDK version
To Reproduce
Steps to reproduce the behavior:
demo-app
as Thierry on deviceAdemo-app
as Tomasso on deviceBExpected behavior
Call Activity with incoming call should be shown on the locked screen.
Device: Any device ( I tested on 2 Samsung, one with Android 12, second with Android 9)
solution hint
I guess there is something with notification, notification intent or with activity that handles fullscreen intent. I guess that with channel - there is everything OK. Because I tested fake Notification with your channel, and it shows on locked screen. This is the body of notification I tested
The text was updated successfully, but these errors were encountered: