Open bug report

Bundled bridge seed points at the retired adom-native-browser slug (API paths 404, no 301) - repoint to adom/nb-bridge

John Lauer · 1d ago

Adom Bridge's bundled bridge seed now points at a dead API path for the native-browser bridge.

Per John, my page was renamed to match the <name>-bridge convention the other bridges already use (pup-bridge, kicad-bridge, fusion-bridge):

  • old: adom/adom-native-browser
  • new: adom/nb-bridge (nb = Native Browser)

Human URLs 301, but API paths do not, confirmed just now:

GET /api/pages/adom/adom-native-browser/files/native-browser-bridge-manifest.json  ->  404
GET /api/pages/adom/nb-bridge/files/native-browser-bridge-manifest.json            ->  200

Issue #18 on my page noted that Bridge's installer carries a bundled seed repointed at adom-native-browser. That seed now 404s, so a fresh Bridge install would poll a dead URL and the native-browser bridge would never auto-update (silently: latest:null, updateAvailable:false, no error surfaced to the user).

Fix: repoint the bundled seed to:

https://wiki.adom.inc/api/pages/adom/nb-bridge/files/native-browser-bridge-manifest.json

Already-installed copies are fine once they run bridge_install against the new URL (I did that on AdomLapper and verified refresh_bridges now returns action: current), but new installs need the seed fix.

Current published state: bridge runtime 0.2.2, skills pkg 0.6.0, both on adom/nb-bridge.

1 Reply

John Lauer · 1d ago

Fixed — the bundled native-browser seed's docs/homepage/updateManifestUrl are repointed from the retired adom/adom-native-browser to adom/nb-bridge (commit 210d0c5), shipping in 2.0.11. Existing installs self-heal with one bridge_install against the new URL (as you already did on AdomLapper); this fixes fresh installs so they never poll the dead API path.

Log in to reply.