On WSL2, the browser login flow could complete successfully, but the callback from the browser (running on the Windows host) did not reliably reach the Polar process running inside WSL. This made the CLI appear to hang after environment selection.
This was caused by a loopback mismatch in the WSL2 host/browser callback path (IPv4 vs IPv6 behavior on localhost), where callback delivery and listener binding were not aligned.
The fix is pretty straightforward: align the callback listener and callback target to the same loopback behavior so both sides use a consistent path. In practice, this removes the IPv4/IPv6 mismatch in the WSL2 callback flow and makes delivery reliable.
Fixed in PR: #16
Thanks!
On WSL2, the browser login flow could complete successfully, but the callback from the browser (running on the Windows host) did not reliably reach the Polar process running inside WSL. This made the CLI appear to hang after environment selection.
This was caused by a loopback mismatch in the WSL2 host/browser callback path (IPv4 vs IPv6 behavior on localhost), where callback delivery and listener binding were not aligned.
The fix is pretty straightforward: align the callback listener and callback target to the same loopback behavior so both sides use a consistent path. In practice, this removes the IPv4/IPv6 mismatch in the WSL2 callback flow and makes delivery reliable.
Fixed in PR: #16
Thanks!