Bump gmessages fork to upstream v26.06 (auth-refresh retry fix)#73
Merged
Conversation
Rebase MaxGhenis/gmessages (ListConversationsWithCursor) from its 2026-03-02 base onto upstream mautrix/gmessages main, picking up 27 upstream commits — most importantly 'libgm/longpoll: retry on network error when refreshing auth token' (2026-05-05), which is the likely root cause of the recurring dead Google sessions: one transient network failure during a scheduled token refresh permanently killed the session (expired token -> HTTP 401 -> needs_repair). Full test suite passes against the new pin. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
MaxGhenis
added a commit
that referenced
this pull request
Jul 3, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Why
Max's Google Messages session has died with
failed to refresh auth token: HTTP 401three times in three weeks (re-paired 6/16, 6/18, dead again since ~6/18). The libgm pin was frozen at the fork's 2026-03-02 base.Upstream landed
libgm/longpoll: retry on network error when refreshing auth tokenon 2026-05-05 — without it, a single transient network failure (laptop asleep, network switch, travel) during a scheduled token refresh permanently kills the session: the token expires, every subsequent refresh 401s, and the session needs cookie surgery or a full re-pair.What
MaxGhenis/gmessages(single fork commit:ListConversationsWithCursor) onto upstreammautrix/gmessages@main(v26.06, 27 commits, clean rebase)replacepin:v0.2602.1-0.20260302032635-a6d7f9898a99→v0.2602.1-0.20260703132304-0e43542dfa0eTesting
go build ./...cleango test ./...passes (all packages)Pairs with the macOS cookie self-healing PR — together: transient refresh failures get retried (this PR), and genuinely expired cookies get refreshed automatically (the other one).
🤖 Generated with Claude Code