Repository navigation
App settings: register the Android device and adopt the bootstrap settings #77
Description
Part of #76 — Companion-app settings sync — register Android under Settings → Applications
- Register on first sign-in:
POST /api/user/app-settings/{appKey}/deviceswith a
human-readable device name (reuse thedeviceLabelalready sent onsync-token, so the same
device reads consistently in both Sessions and Applications). - On a brand-new install, seed from
GET /api/user/app-settings/{appKey}/bootstrap?deviceId=—
the web's stated behaviour is that a new machine starts from the main workstation's
settings. - Deregister on sign-out / account deletion.
Tests: register → device appears; bootstrap seeds a fresh install.
Filed from the parity review of feature/parity-wip @ 14d7795 against interlinedlist.com (OpenAPI /api/openapi.json, 233 paths) and the public help centre.
Activity
Adron commentedon Sep 16, 2026
Implemented in the PR above (branch
issue/77-app-settings-register). Closing here — review and any follow-up happens on the PR.appKeyisinterlinedlist-androidand must never change — the key is the namespace, so changing it would orphan every device registration and settings document under the old one. It is free-form (no registration step); the web's own first consumer usesvisual-introspection, so the convention is a human-readable slug.The device label the issue asked to share is now genuinely shared:
DefaultAuthRepositorywas computing"InterlinedList Android · ${Build.MODEL}"inline forsync-token, and that now comes from aDeviceLabelProviderreused as the registry'sdeviceName— so the same phone reads identically under Sessions and Applications.A real bug surfaced during probing: kotlinx.serialization omits a property equal to its default, so
platformwas being stripped from the registration body, which the live API rejects with400 "platform is invalid".One piece of residue I could not clean up: the live probe used a throwaway
appKeyzz-probe-77-scratch. Its devices and documents are all deleted and verified gone, but the shared app-catalog entry it created (display name "Probe 77 (delete me)") has no public delete endpoint —DELETE /api/user/app-settings/zz-probe-77-scratchanswers{"deleted":false}. It may appear as an empty extra row in the web's Settings → Applications and would need a server-side delete.merge: #77 companion-app device registration (PR)