Symptom
When running hoot and choosing "Scan QR with Amber", users see error messages that don't tell them what's wrong:
"web socket failure, response, no exception, no [response yet]"
It does log them in eventually, but the failure path is opaque: the user can't tell whether it's their relays.txt, a proxy env var, a dead relay, or just Amber not approving fast enough.
Where the strings live
nip46/nip46.go:371 — bare "no response yet" returned by Session.CheckConnection after a 3-second polling timeout. No actionable context.nip46/nip46.go:242 — "could not connect to any relay (tried: ...)" discards the per-URL dial error. Users with stale relays.txt have no clue which line to remove.tui/tui.go:564-573 — initQR swallows the error from OnInitQR via return nil. The user is left staring at "Generating connection..." forever with no message.
The substring "web socket failure" itself is not in the source — it's either a wrapped go-nostr error, a stale binary from before PR #69/70/73/74/75, or the user truncated the paste.
Fix
The branch fix/nip46-signin-error-message addresses all three call sites. See the PR for full details.
Symptom
When running
hootand choosing "Scan QR with Amber", users see error messages that don't tell them what's wrong:It does log them in eventually, but the failure path is opaque: the user can't tell whether it's their relays.txt, a proxy env var, a dead relay, or just Amber not approving fast enough.
Where the strings live
nip46/nip46.go:371— bare"no response yet"returned bySession.CheckConnectionafter a 3-second polling timeout. No actionable context.nip46/nip46.go:242—"could not connect to any relay (tried: ...)"discards the per-URL dial error. Users with stale relays.txt have no clue which line to remove.tui/tui.go:564-573—initQRswallows the error fromOnInitQRviareturn nil. The user is left staring at "Generating connection..." forever with no message.The substring "web socket failure" itself is not in the source — it's either a wrapped go-nostr error, a stale binary from before PR #69/70/73/74/75, or the user truncated the paste.
Fix
The branch
fix/nip46-signin-error-messageaddresses all three call sites. See the PR for full details.