Skip to content

Fix Android server-connected profile saves - #301

Open
sacgsxr wants to merge 1 commit into
TraceApps:mainfrom
sacgsxr:fix/android-profile-save
Open

sacgsxr wants to merge 1 commit into
TraceApps:mainfrom
sacgsxr:fix/android-profile-save

Conversation

@sacgsxr

@sacgsxr sacgsxr commented Oct 26, 2026

Copy link
Copy Markdown

On Android connected to a server, saving the Profile page fails with “Could not save profile” before any request reaches the server. Profile.svelte calls NtApi.updateProfile, but the selected NtApiCached implementation does not provide that method.

Add NtApiCached.updateProfile through the existing authenticated PUT transport. Birthday, gender and the remaining account fields are sent to /api/auth/profile, and the confirmed server user is returned to the screen. The web/PWA and native standalone paths keep their existing behavior.

Validation:

  • New behavioral regression test reproduces the missing-method failure before the fix and passes afterward. It checks the request URL, PUT body, bearer authentication, returned account identity, and auth/network error propagation. Test records are synthetic.
  • Offline wiring: 22 tests pass. Offline edits: 37 tests pass. Account scope: 2 pass, 5 skipped because native SQLite is unavailable in the local test environment.
  • Production Vite/PWA build and git diff --check pass.

Android users need a signed APK release containing the fix; updating only the server does not replace the bundled client code.

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