Open
Description
To reproduce:
- Run noflo-browser with noflo-runtime-webrtc. Specify a fixed runtime ID
- Open the runtime in Flowhub via live URL, go to project mode
- Observe connected OK to runtime
- Close Flowhub, restart the runtime
- Open the runtime in Flowhub via live URL, go to project mode
Expected: Connects to runtime in same way as first time, using WebRTC
Actual: Does not connect over WebRTC. Instead a new noflo-browser iframe runtime is loaded
This only happens if the runtime ID is the same as one previously used. This leads me to believe that the connection details are being overwritten somewhere.
Workaround: Always generate a new runtime ID
Activity