Repository navigation
G1 Install and update: Install, sign in and recover #88
Description
Release: 0.8.0.
Owner: Anders (@andersalm). Sasha owns the installation page. Required.
Targets: Linux x86-64, Apple Silicon Mac and Jetson Orin Nano.
Done means
Release acceptance: Each exposed feature works clearly from start to end, including recovery. Keep unfinished or confusing features hidden until their complete journey passes. Hiding a feature does not complete its task; source checks alone do not establish installed acceptance.
- The website supplies the correct signed Runtime for each supported target. Proof: G1 Install and update: Install, sign in and recover #88 (comment)
- A fresh install reaches Home, passkey sign-in and Profile through ordinary use. Test: on a clean Mac, Linux x86-64 and Jetson account, run
curl -fsSL https://elastos.elacitylabs.com/install.sh | bash; Home opens; sign up with a passkey; lock; sign in with the passkey; open Profile and check the name and DID. Earlier Linux runs: alpha.16 proof, alpha.24 Linux 11/11. Open: fresh install on the 0.8.0 candidate on Mac and Linux x86-64; Jetson fresh install is a post-publication install step. - A Recovery Kit restores the same identity on a second machine. Test: after PR Signed-in devices, a 30-day sign-in limit, and Recovery Kit restore on a new computer (#88) #355, on Home A save the Recovery Kit; install on a second clean machine, choose restore and import the Kit; Profile shows the same DID and name.
- Moved to 0.8.1: 0.8.1: List and revoke your own sessions, with a maximum sign-in age #363 (list and revoke your own sessions, maximum sign-in age; draft PR Signed-in devices, a 30-day sign-in limit, and Recovery Kit restore on a new computer (#88) #355).
- Recovery Kit import keeps an administrator and never promotes a guest: tests cover owner recovery on the same Home, registration turned off, and a guest importing a foreign kit. Proof: https://github.com/Elacity/elastos-runtime/blob/aa3d61e4478a1a1a63dbef0dae97c23a0f9f4851/elastos/crates/elastos-server/src/auth.rs#L2508, https://github.com/Elacity/elastos-runtime/blob/aa3d61e4478a1a1a63dbef0dae97c23a0f9f4851/elastos/crates/elastos-server/src/auth.rs#L9870 and https://github.com/Elacity/elastos-runtime/blob/aa3d61e4478a1a1a63dbef0dae97c23a0f9f4851/elastos/crates/elastos-server/src/api/auth_gateway.rs#L8154
- Owner recovery on the same Home:
elastos identity arm-owner-recoverywith the Recovery Kit and a terminal code (delivered in alpha.15). Proof: 71e9ce5fc Test: on alpha.15, with every passkey removed, choose "Recover this Home with your Recovery Kit", run the command shown, enter the code, and sign in as owner. - Fresh install and supported upgrade use the installation layout and
preservation rules accepted by UP-02 (UP-02: Stage one complete release #108)/03/07. Proof: UP-07: Accept updates on Mac, Linux and Jetson #113 (comment) - Sasha accepts the installation instructions (including the board-local security-key sign-in doc, First-time setup dead-ends at the passkey step on Windows and Linux #452) and first-run experience.
Remaining install/update work for 0.8.0: #89 Remaining for 0.8.0.
Activity
andersalm commentedon Sep 29, 2026
Retained test input from the installation and recovery notes:
These are regression inputs within this issue, not claims that old failures remain on the current candidate.
andersalm commentedon Sep 29, 2026
QA retest 2026-09-29 opened two hosted first-run findings under this release issue:
runtime/ensureidentity-path ownership after guest sign-in (Notion QA-49)Also commented on #86 (lock-face Create guest / Use passkey 0×0 — QA-30) and #89 (published 0.1.2 vs release-head 0.7.1 / marketing coming soon — QA-47).
andersalm commentedon Sep 29, 2026
QA tip retest on
feat/0.7.1-models@b1a22a6e(2026-09-29) — still broken; filed child issues under this install/setup row:elastos shareENOENT / documents missing rootindex.html(Notion QA-31; also touches After 0.8.0: Protected content #91/0.8.0: Release 0.8.0 #93)setup --profile demofails on emptymedia-toolschecksum (tunnel-providerempty too) (Notion QA-44)Evidence:
/workspace/elastos-qa/github-reset-20260929/retest-models/RETEST.md[-]0.7.1: Install, sign in and recover[/-][+]0.8.0: Install, sign in and recover[/+]andersalm commentedon Oct 1, 2026
QA Deployment 2026-10-01 — hosted surface down
https://elastos.elacitylabs.com/and/home/return HTTP 502 (nginx Bad Gateway) from the Deployment slot box. Blocks hosted install/sign-in/recover smoke on the public Home.Filed with update-channel symptoms: #162. Also affects #89 release-head fetch.
andersalm commentedon Oct 12, 2026
Evidence (12 Oct, published 0.8.0-alpha.15, fresh machines,
curl -fsSL https://elastos.elacitylabs.com/install.sh | bash): Linux x86_64 and Linux arm64 (Ubuntu 24.04, non-root) and Apple silicon Mac each installedelastos 0.8.0-alpha.15verified against the maintainer DID;elastos update --checkreports up to date; Home sign-up passes (2.2 s, 2.5 s, 1.6 s). Jetson hardware run follows.[-]0.8.0: Install, sign in and recover[/-][+]G1 Install and update: Install, sign in and recover[/+]andersalm commentedon Oct 13, 2026
Jetson Orin Nano, alpha.15: fresh install passes (about 5 minutes). The first run refused because the account's
~/.local/sharewas group-writable (umask 0002);chmod go-w ~/.local/sharefixed it.andersalm commentedon Oct 13, 2026
Postponed to 0.8.1: session list/revoke is in draft PR #355; not needed to install and use. Moved to #363.
andersalm commentedon Oct 14, 2026
Codex (agent): Ordinary published alpha.16 source 703c8f4 installation took 132.429/134.094 s on Linux x86_64/ARM64; passkey signup took 0.318/0.802 s. Recovery Kit download and Profile Save passed.
Native Linux browsers used virtual passkeys. Candidate Lock/sign-in, Mac/Jetson first-run acceptance, second-machine Recovery Kit restore and Sasha's acceptance remain open.
andersalm commentedon Oct 14, 2026
RC 0.8.0-alpha.16, Jetson fresh install (Anders, 14 Oct): the Recovery Kit download step in first-run onboarding failed when the Home ran as a different OS user than the browser (Brave). Signup itself worked. Not blocking 0.8.0; follow-up in 0.8.1.
andersalm commentedon Oct 14, 2026
Correction to the 15:46Z comment: the "different OS user" cause was wrong (the kit is a browser Blob download). Likely cause: on a cold first-run Runtime, System answers the setup sheet only after five startup fetches, past the shell's 15 s limit, so "Save Recovery Kit" reports not saved. Any user can hit it, so it is fixed in 0.8.0-alpha.17 (fix/080-recovery-kit-ready). Open for 0.8.1: the step is marked done before the browser saves the file.
andersalm commentedon Oct 14, 2026
Update from Anders: the Recovery Kit file was saved; what broke is that the onboarding sheet disappeared after the first button (System opened) and never came back, so the user loses the remaining setup steps. The 15 s cold-start theory above is unconfirmed. alpha.17 fix targets the sheet not returning (fix/080-recovery-kit-ready).
andersalm commentedon Oct 15, 2026
RC 0.8.0-alpha.17 (source 37df2f6), fresh test-channel install, Linux x86_64 + ARM64 Namespace boxes (Ubuntu 24.04, non-root): PASS. install.sh 136.7 s / 84.7 s (earlier runs 80.0 s / 77.5 s), passkey sign-up 1.0 s / 2.3 s.
Welcome sheet: Save Recovery Kit downloads the kit, sheet returns with step 1 done ("Ready", "Home is set up."); opening Chat from it shrinks it to a card (420x467 -> 360x290); clicking the card restores it. Both arches.
andersalm commentedon Oct 15, 2026
Pre-signing check on eeda0aa (two Linux Homes, real Chromium, virtual passkeys): first lost-passkey recovery with a Kit works end to end (same principal, Profile, new passkey admin, old refused). Known issue (0.8.1 fix in progress): a second recovery with the SAME Kit on that Home, or after importing that Kit in System, shows "could not finish" because the outcome audit event id collides (auth.rs:6384-6402, auth_gateway.rs:1951-1989); the account IS recovered, a page reload shows it. Also: a fresh Home accepts another Home's Kit by design (auth.rs:6317-6339); the alpha.15 notes wording overstates the refusal.
andersalm commentedon Oct 16, 2026
Installed alpha.19 on Mac: sign-up, welcome sheet card, lock -> passkey sign-in (same Profile and DID), System Import of the saved Kit, sign-in picker accepts the Kit: PASS. Non-blocking (0.8.1): the Kit file name contains a literal ellipsis (
elastos-recovery-person…2d4b36.json, shortText in system.js:3312); the sign-in file field still says "No file chosen" after a Kit is selected; people/summary reports recovery_kit_outdated after an import until the Kit is saved again.andersalm commentedon Oct 16, 2026
Remaining for 0.8.0 (15 Oct 22:45 COT; final candidate alpha.21 = alpha.20 + automatic Community recovery; plan #93 6207232773): Jetson fresh install of alpha.21 with sign-up -> lock -> passkey sign-in (or the owner moves the Jetson part to the 0.8.0 fresh-install check after publication); Sasha's first-run acceptance (#93). Known issues for 0.8.1: repeat Kit recovery (fix ready), Kit file name.
andersalm commentedon Oct 16, 2026
Ticked with proof: Recovery Kit restore on a second machine: on installed 0.8.0-alpha.19, Home A's Kit restored on a fresh Linux ARM64 Home gave the same Profile DID and name (#89 6205121022, run evidence a19-linuxpair-20261016T0022Z). Still open: box 1 needs the Jetson fresh install (Mac and Linux passed: #88 6204914758, #89 6205121022) and Sasha's acceptance.
changelog: 0.8.0 notes match what a new user gets: phone layout reach…
andersalm commentedon Oct 16, 2026
Removed stale prose from the fresh-install box (alpha.16 preparation timings and 'Recovery Kit restore remains open', which contradicted the ticked box); linked the alpha.16 proof instead. Fresh install on the 0.8.0 candidate (Jetson as a post-publication step) and Sasha's acceptance remain open.