Willi Sontopski

Thank you for your quick answer. Is there a chance, that a future version of your parser supports the syntax I mentioned above?

I have the same issue. I fixed it used the option `enableForceNewConnection` on socket creation. Example: ```dart socket = io(EnvVar.SERVER_URL, OptionBuilder() .setTransports(['websocket']) // for Flutter or Dart VM .enableForceNewConnection() //...

I had the same problem with `socket_io_client: ^2.0.0-beta.4-nullsafety.0`, `nginx` and `flask-socketio==5.1.0`. But the fix provided by @kameshkarthi works fine for me. Thank you so much!

Okay thx, but I thought there would be an easier way.

@Lyokone Could you review the merge request soon please? This is a huge issue for our app. Thanks!

Maybe requesting the location a second time is valid workaround for this. The first, the `Future` of `getLocation()` does not return, but the second time it does. So instead of...

@AlpSha Yes, I think you are right. The problem seems to different on different platforms. I had this problem on bith Android and iOS. On Android, the second call is...

I have the same problem :(

I've found a workaround for this: https://github.com/Lyokone/flutterlocation/issues/621#issuecomment-931597019

Let's remove the `inactive` label, because only the maintainer is inactive.