Repair Farcaster admission alerts and smooth Mini App zoom - #186
Merged
Conversation
ael-dev3
force-pushed
the
codex/farcaster-notification-zoom
branch
from
August 3, 2026 20:23
20b2588 to
ad0e1c0
Compare
ael-dev3
force-pushed
the
codex/farcaster-notification-zoom
branch
from
August 3, 2026 20:30
ad0e1c0 to
dee674c
Compare
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.
What changed
failedTokensnotification response while preserving strict validation of known outcomesWhy
Farcaster added optional per-token failure metadata in April 2026. Warpkeep's exact response parser treated that additive field—even
failedTokens: []—as an invalid response, leaving successful admission alerts in the retry queue. Mini App pinch input was also too sensitive in mobile WebViews.Validation
No SpacetimeDB schema or player-state code changes are included.