Socket triggered::connect_error

[MusabAbid]

Describe the bug
W/.flutter_rwtap( 5678): Accessing hidden method Ldalvik/system/CloseGuard;->get()Ldalvik/system/CloseGuard; (light greylist, reflection)
W/.flutter_rwtap( 5678): Accessing hidden method Ldalvik/system/CloseGuard;->open(Ljava/lang/String;)V (light greylist, reflection)
W/.flutter_rwtap( 5678): Accessing hidden method Ldalvik/system/CloseGuard;->warnIfOpen()V (light greylist, reflection)
D/Adhara:Socket( 5678): Socket triggered::connect_error
I/flutter ( 5678): onConnectionError io.socket.engineio.client.EngineIOException: websocket error

Have you tried reproducing the issue with example available in this repo?
Yes/No?
No
To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Device details:

• Device Type: Emulator
• Model: Nexus 5S api28
• OS: Window 10
• Package Version:adhara_socket_io: ^0.4.2+1

Relevant Logs

Add any relevant logs about the problem here.

[AbdullahGaber]

have you solved this issue?

[MusabAbid]

No it doesn't work so i just leave it and use Firebase Firestore

…

On Tue, Mar 30, 2021, 5:22 PM AbdullahGaber ***@***.***> wrote: have you solved this issue? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASIDDPAC22Y62BBNSU2XKKLTGG7AFANCNFSM4WCPGWJQ> .

[AbdullahGaber]

No it doesn't work so i just leave it and use Firebase Firestore

On Tue, Mar 30, 2021, 5:22 PM AbdullahGaber @.***>
wrote:

have you solved this issue?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#146 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASIDDPAC22Y62BBNSU2XKKLTGG7AFANCNFSM4WCPGWJQ
.

In my case, the problem was from backend he didn't run the socket server

[tiholic]

@MusabAbid @AbdullahGaber this issue could be due to usage of incompatible sever side socket io version.
Currently the package supports only v2 socket.io

track v3/v4 support here: #160