mirror of
https://github.com/safijari/openpuck.git
synced 2026-11-03 22:30:22 +00:00
[PR #129] [MERGED] fix: waitReconnect detects puck reappearance without auto-connect (Android Chrome) #219
Labels
No labels
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
safijari/openpuck#219
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
📋 Pull Request Information
Original PR: https://github.com/safijari/openpuck/pull/129
Author: @Copilot
Created: 7/5/2026
Status: ✅ Merged
Merged: 7/5/2026
Merged by: @safijari
Base:
main← Head:copilot/handle-puck-reconnection📝 Commits (1)
5367249fix: detect puck reappearance in waitReconnect for Android Chrome📊 Changes
1 file changed (+20 additions, -2 deletions)
View changed files
📝
docs/index.html(+20 -2)📄 Description
On Android Chrome,
openDevice()requires a user gesture, soautoConnect()silently fails after the firmware update reboot.waitReconnect()was gated ondev && _lastBlobTs > t0— a condition that can never be true without a successfulopenDevice()— causing the updater to hit the 40 s timeout and show a failure modal even when the update applied cleanly.Changes
waitReconnect()— after observing the disconnect (seenGone), now also pollsnavigator.usb.getDevices()each iteration. Returns"appeared"if the puck is back in the authorized-device list butdevis still null (auto-open failed); returnstrueon full reconnect+blob as before;falseon genuine timeout.runUpdate()— handles the new"appeared"outcome as success, showing "Update applied — the puck is back. Tap Connect to reconnect." instead of the bogus error.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.