Recover Google Messages auth without re-pairing - #19
Merged
Conversation
Phloraxx
marked this pull request as ready for review
July 27, 2026 10:04
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
1 participant
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.
Superseded by current
main.The Google Messages recovery implementation from this branch is already present in the current
mainhistory, including:reauth_requiredstate on Google auth expiryPOST /api/connector/gmessages/reauth/googleCurrent
mainhas since advanced with additional August operational/payment changes, so this old divergent branch must not be merged. The temporary self-writing workflow on this branch is also intentionally not part ofmain.Live verification on 2026-08-13 confirmed the production reauth route exists and validates cookie input safely.