Dee
Dee
@maheshmnj awesome now you see the bug. It's also the same for release mode. We cannot use Firebase on MacOS because of this, no customer is going to accept a...
@Aksi0 yes Aksi0, because we are signing a release version via the store. So I don't think this is a fix.
@tommienu we're not using ```crashalytics``` fyi, just Firebase messaging.
@tommienu indeed, this library, not good that they are forcing us to use this library to do Push Notifications on Android (because we had the nice and simple GCM). Otherwise...
Did anyone mange to resolve this over App Engine? Sockets are working for everything except Web over WSS. Web with debug is working with WS & Local. I'm using ```socket_io_client:...
Dam, we're stuck at the moment cause we can't specify a port on the domain. Sucky bug! Has someone made a PR yet?
It's a quick fix on the library if you download it. (If someone can make a PR) Change ``var id = '${parsed.scheme}://${parsed.host}:${parsed.port}';`` To ``` String port = parsed.port != null...
@RukshanJS it's been very solid for us, on all platforms (Web, Android, iOS, MacOS, and Windows) using it on production feels a bit risky though.
I find that if you call disconnect, destroy or dispose it never works again, instead we just do this `_socket?.clearListeners();` Then remake it.
@huydq88 nah Flutter is booming, just this library needs some love