fix(core): guard undefined navigation queue entry in Frame - #11326
Open
NathanWalker wants to merge 1 commit into
Open
fix(core): guard undefined navigation queue entry in Frame#11326NathanWalker wants to merge 1 commit into
NathanWalker wants to merge 1 commit into
Conversation
|
View your CI Pipeline Execution ↗ for commit cafe076
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
CatchABus
requested changes
Aug 1, 2026
A goBack() queued while another navigation is still executing (e.g. an interactive dismiss that finished out-of-band) can leave the head of the navigation queue without an entry, since performGoBack hasn't populated it yet. Skip the head safely instead of crashing on reading `.resolvedPage`.
NathanWalker
force-pushed
the
fix/frame-navigation-queue-guard
branch
from
August 3, 2026 20:28
a348784 to
cafe076
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
2 participants
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.
A goBack() queued while another navigation is still executing (e.g. an interactive dismiss that finished out-of-band) can leave the head of the navigation queue without an entry, since performGoBack hasn't populated it yet. Skip the head safely instead of crashing on reading
.resolvedPage.