fix!: navigation session error handling #502
Merged
Conversation
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
jokerttu
force-pushed
the
fix/error-handling-for-navigator-methods
branch
from
7c32c36 to
ff991e1
Compare
jokerttu
force-pushed
the
fix/error-handling-for-navigator-methods
branch
from
ff991e1 to
ddaa3db
Compare
illuminati1911
approved these changes
Nov 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Improves error handling and guards for navigation session method calls.
Adds
NO_DESTINATIONSerror for android implementation if start guidance is called without destinations set.Adds detox tests.
BREAKING CHANGE:
no_destinationserror string on iOS is changed toNO_DESTINATIONSmatching other error code formats and Android implementationFixes #498
Pre-launch Checklist