fix: useAgnosticNavigation error when we reach an ErrorBoundary - #1212
Merged
ChibiBlasphem merged 1 commit intoNov 20, 2025
Merged
Conversation
ChibiBlasphem
force-pushed
the
fix/agnostic-navigation-provider-error-when-error-boundary
branch
from
November 20, 2025 13:26
cf9713b to
25fd0e5
Compare
ChibiBlasphem
deleted the
fix/agnostic-navigation-provider-error-when-error-boundary
branch
November 20, 2025 13:32
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.
When app was triggering an ErrorBoundary AgnosticNavigationProvider wasn't present in the react tree causing this error to be displayed instead of the error actually happening