Repository navigation
Recover Captain sign-in after desktop reinstall - #225
Merged
Merged
Conversation
sridharkalaibala
marked this pull request as ready for review
October 30, 2026 20:33
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.
Captain could become stuck after a till reinstall because a missing paired session was reported as an offline server. Rejected or expired password-only logins also lacked an in-place recovery prompt, and reconnecting could retain obsolete pairing secrets.
Offer sign-in at the saved issuing address, retain saved orders and addresses, and replace old credentials only after validating the same shop, staff member and branch. Keep revoked-device and unverified-route protections intact. A successful recovery permits another prompt after a later reinstall.
Validation completed locally:
npm run check).Sync: existing secure local credentials only. No business schema, Gateway or sync-agent changes; session secrets remain local. Existing POS APIs suffice. Rollout requires the updated Captain APK.
The earlier disk-space blocker has been resolved and the complete local gate has now passed.
Published signed testing APK: https://github.com/Posnic/captain/releases/tag/captain-1.3.72-test.1 . Built from merged main 573770a, version 1.3.72 (10372); signing certificate matches 1.3.71. Uploaded APK digest matches the local SHA-256.