Skip to content

fix(activesync): handle missing synckey in error handler#17

Closed
ralflang wants to merge 1 commit into
FRAMEWORK_6_0from
fix/defensive-synckey-handling
Closed

fix(activesync): handle missing synckey in error handler#17
ralflang wants to merge 1 commit into
FRAMEWORK_6_0from
fix/defensive-synckey-handling

Conversation

@ralflang
Copy link
Copy Markdown
Member

Treat missing synckey as requiring state reset (like initial sync).
Asking for state reset may be wasteful but from what I read it's safe to do mostly.

In EAS protocol, synckey '0' means initial sync. Missing synckey is fishy.
It indicates a protocol error that occurred before synckey was parsed.
Trigger synckey reset to establish a new valid state.

See also: MS-ASCMD synckey semantics for initial vs subsequent sync

Treat missing synckey as requiring state reset (like initial sync).
Asking for state reset may be wasteful but from what I read it's safe to do mostly.

In EAS protocol, synckey '0' means initial sync. Missing synckey is fishy.
It indicates a protocol error that occurred before synckey was parsed.
Trigger synckey reset to establish a new valid state.

See also: MS-ASCMD synckey semantics for initial vs subsequent sync
@ralflang
Copy link
Copy Markdown
Member Author

Closing: This change is already included in commit 07454f8 which was merged to FRAMEWORK_6_0. The comprehensive fix includes all error handler hardening changes (synckey, ID, class, and logging).

@ralflang ralflang closed this Mar 21, 2026
@ralflang ralflang deleted the fix/defensive-synckey-handling branch March 21, 2026 13:56
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