-
Notifications
You must be signed in to change notification settings - Fork 90
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
Session problems #22
Comments
we are working on this problem now, we will release new version in near few days |
Hi @TatankaConCube, tnx for quick response. Is the issue in ConnectyCube SDK or in example? |
jus now we released a new version of our SDK, please find out our documentation to organize reconnection logic in your app |
@TatankaConCube We have just tested it with 0.4.0 version and it seams the issue is resolved. Thank you so much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specify the sample to which the issue belongs (use [x]):
[x ] P2P Call sample
[ ] Conference Call sample
Platform (use [x])
[ ] Android
[ x] iOS
Describe the bug:
We started integration of ConnectyCube SDK for Flutter in one of our products. But we have a serious issue with the chat/call sessions. After the user is logged in and the device is locked for more than 30 seconds, the SDK stop to provide events for incoming call sessions. The chat stops working as well. I’ve tried to re-log in the user, after app becomes active again, but this fix didn’t work for me.
Steps to Reproduce:
Actual result:
Won’t receive the incoming call
Expected behavior:
Receive incoming call
Additional info
I also find next problem. If the user is re-logged in it will not receive the incoming call. Step to reproduce:
I think the problem in both situations is the same.
Can you provide us a solution for this problem(s)?
The text was updated successfully, but these errors were encountered: