Skip to content

Keep identity across launches and back it up in Supabase - #43

Merged
ucguy4u merged 1 commit into
mainfrom
feat/persist-identity
Oct 23, 2026
Merged

ucguy4u merged 1 commit into
mainfrom
feat/persist-identity

Conversation

@ucguy4u

@ucguy4u ucguy4u commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The identity form now saves itself on the phone, so a relaunch no longer starts from an empty form.
  • The same profile is stored in Supabase. Another device claims it with the recovery code. Purchased avatar items still come back through Store → Restore purchases on the same Google account.
  • Crashes are written on device. The webhook worker can accept them, and the Supabase tables for crashes and profiles are in the repo.

Test plan

  • Identity screen tests, including autosave and reopening a saved identity
  • Crash reporter tests
  • Identity id tests
  • Install 1.0.4 from the Play internal track and confirm the form stays filled after a force-stop
  • On a second phone, restore the profile with the code and restore purchases with the same Google account

Made with Cursor

The form only saved when Save was tapped, and only on that phone, so a reinstall asked for the same details again. Autosave writes the local record as the person types, and an anonymous Supabase profile plus a recovery code restores the name and avatar on another device. Purchases still follow the Google account through Restore purchases. Crashes are recorded on device, with a worker route and table ready for ingest.

Co-authored-by: Cursor <cursoragent@cursor.com>
@ucguy4u
ucguy4u merged commit 2f9d6c8 into main Oct 23, 2026
2 checks passed
@ucguy4u
ucguy4u deleted the feat/persist-identity branch October 23, 2026 08:46
cursor Bot pushed a commit that referenced this pull request Nov 2, 2026
Clarify foundation-era stub wording in overview.md, fix app_links
reference to sharing_providers.dart, and align TODOS catalog count and
Supabase profile backup wording with #43.

Co-authored-by: Uday Chauhan <chauhan.s.uday26@gmail.com>
cursor Bot pushed a commit that referenced this pull request Nov 2, 2026
…#43)

Co-authored-by: Uday Chauhan <chauhan.s.uday26@gmail.com>
ucguy4u added a commit that referenced this pull request Nov 2, 2026
* docs: align READMEs and status docs with shipped sharing and store

Co-authored-by: Uday Chauhan <chauhan.s.uday26@gmail.com>

* docs: address architect nits on overview, identity-link, TODOS

Clarify foundation-era stub wording in overview.md, fix app_links
reference to sharing_providers.dart, and align TODOS catalog count and
Supabase profile backup wording with #43.

Co-authored-by: Uday Chauhan <chauhan.s.uday26@gmail.com>

* docs(TODOS): align completion engine credits with shipped APIs

Replace references to completedSeries/isSetComplete/collectedCosmeticIds
with collectionProgress, CollectionProgress.isComplete, SeriesCompletion.isComplete,
and buildShareUri so the doc stays accurate when dead-code PR #45 lands.

Co-authored-by: Uday Chauhan <chauhan.s.uday26@gmail.com>

* docs(TODOS): fix §9 share history after #18 encounter cutover

Replace incorrect live-path claim (buildShareUri) with dated legacy
amiro://share wording and current amiro://encounter payload via
buildOwnEncounterUri, per architect review.

Co-authored-by: Uday Chauhan <chauhan.s.uday26@gmail.com>

* docs: align legal copy and worker README with Supabase profile backup (#43)

Co-authored-by: Uday Chauhan <chauhan.s.uday26@gmail.com>

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant