-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Voice and Video call error after click notification when app is on background #7031
Comments
When the device is not locked it's normal to be navigated to the app. |
All i did was just clone the repo and change homeserver, change bundle id, change provisioning. |
This issue was the follow up from this closed issue in sygnal github issue |
update: |
@ismailgulek Hi could you please check the PR and approve. |
@febryituery did you get any issue like 4-6 empty push notifications coming along with ringing voip notification? |
Steps to reproduce
Where are you starting? What can you see?
I clone this repo and change homeserver with my own server and configuration. I did configure everything from APNs to sygnal config
What do you click?
I tried regular chat notification and it worked. And then when i tried voice or video call, notification show up, but when i click accept, it redirect to app and then terminated.
More steps…
So when app is on background but app still alive (not in terminated state), duration of notification shows like normal. But when app is on background but app is terminated, notification only show like 3 second and then dissapear.
Also got this error message from xcode
Outcome
What did you expect?
Voice and Video call work like a charm after clicking from notification tray when app is on background
What happened instead?
When notification arrive, i clicked accept and then it redirect to app and then terminated. So i can't receive voice or video call from background state
Your phone model
iPhone 11
Operating system version
16.1
Application version
1.9.7
Homeserver
Matrix.org
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: