fix(channel): diagnostics for a pairing that never completes, and 201 for watches up to v0.5.0 #62
Loading…
Reference in a new issue
No description provided.
Delete branch "relay-old-watches"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A pairing that ends with "the watch hasn't answered" says nowhere why. The watch runs v0.5.1, and the relay and its proxy work end to end: I acted out a pairing by hand against production, and the message reached the waiting poll the moment it was sent. So this PR makes the next attempt show where it stops, from both ends.
Relay request log (
RELAY_LOG=1in the app panel's environment;compose.yamlpasses it on):{id}for the channel, the status, the time taken, and a poll's number of messages.docs/dev/deployment.md#relay-logshows what a working pairing looks like in the log.Pairing screen on the watch: a line under "Pairing" shows what the link is doing, or what last went wrong:
Creating the channel/Channel created (201)/Waiting for the phone;Relay not reached (code),Poll failed (code), orno phone (-104)without a Bluetooth link to Garmin Connect;Message refused: wrong key / clocks apart / replayed / malformed, orMessage broke: …when opening the viewer's message throws. Until now such messages were dropped silently.Also: the relay answers 201 with
{}again for a channel created again. The watch apps up to v0.5.0 accept only 201, 204 or 409 there, and the viewer creates the channel first in every pairing. This doesn't affect v0.5.1.Not tested on a device: the watch changes are compiled by CI only. The relay log has tests, including one that checks the event stream still flushes through it.
fix(relay): 201 for a channel created again, which watch apps up to v0.5.0 needto fix(channel): diagnostics for a pairing that never completes, and 201 for watches up to v0.5.0