-
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
Showing START CALL NULL in IOS #6
Comments
hello @sathvikrijo, please provide us full log from flutter console from app start to getting this issue (from caller and receiver side). |
Hi @TatankaConCube, I receive the same issue on iOS. However, to be sure that it works on Android I tested it on 2 simulators Pixel 2 (Linux Mint) it worked well. Performing hot restart... flutter: State: XmppConnectionState.ReceivingFeatures flutter: response: <xmpp_stone><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' from='chat.connectycube.com' id='8dc3fb4d-01ea-4d03-a646-76d9f2969c41' version='1.0' xml:lang='en'></xmpp_stone> flutter: State: XmppConnectionState.Authenticated |
hello guys, thank you for reported issue. Please don't filter logs. Instead of it collect full logs from both sides (caller and receiver) and send them to support@connectycube.com if you don't want show private data on github. In subject of letter please set title from this issue. |
Hi, I just want to mention that I tested it on a physical iOS device and it worked well. However, it didn't work on iOS simulators. iPhone 8 and iPhone SE. |
Did you test another apps with WebRTC calls on iOS emulators? |
Seems there is no much activity out there. Closing the issue as stale. If it’s still actual - please raise a new one. |
throwing the error as "start call null" in the console after accepting the call or trying to start the call in IOS. Help me
The text was updated successfully, but these errors were encountered: