The wasm client on the main branch has two issues:
After #297, the client no longer works. The wasm timer dependency for handling timeouts caused the wasm app to not launch due to relying on some API that isn't supported. This needs to be replaced.
Apparently wasm subprotocols cannot have slashes.
After disabling the timeout code in wasm and changing the subprotocol to something different, the wasm client works again.
I want to look into when I last changed the subprotocol to determine if 0.4 had the same subprotocol, or maybe it didn't use the subprotocol yet.
The wasm client on the main branch has two issues:
After disabling the timeout code in wasm and changing the subprotocol to something different, the wasm client works again.
I want to look into when I last changed the subprotocol to determine if 0.4 had the same subprotocol, or maybe it didn't use the subprotocol yet.