Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 selectedNtApiCachedimplementation does not provide that method.Add
NtApiCached.updateProfilethrough 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:
git diff --checkpass.Android users need a signed APK release containing the fix; updating only the server does not replace the bundled client code.