From 43c62c2f338654394f82c86aa12b22be6a358d94 Mon Sep 17 00:00:00 2001 From: Tianren Dong Date: Sat, 16 May 2026 12:56:24 -0400 Subject: 0.17.1: fix /chrome onboard stuck on 'Waiting for the extension to wake up' 0.17.0 made the daemon own the HTTP listener, but the Pi client's bridge.status().connected still reflected the local Pi's lastSeenAt (which is never updated in the daemon model). Onboard's connect-wait loop spun forever even when the extension was polling the daemon. Fix: new ChromeProfileBridge.daemonStatus() async helper that fetches the daemon's /status. onboard, doctor, and status now query that for the 'connected' flag instead of reading stale Pi-side state. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'package.json') diff --git a/package.json b/package.json index 6b38254..1813de4 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "pi-chrome", - "version": "0.17.0", + "version": "0.17.1", "scripts": { "version": "node scripts/sync-manifest-version.js", "prepublishOnly": "node scripts/sync-manifest-version.js" -- cgit v1.2.3