Repository navigation
fix(mobile): handle GO_BACK navigation error with safe fallback - #40
Merged
Merged
Conversation
Fix "The action 'GO_BACK' was not handled by any navigator" error in practice screens. All router.back() calls now check canGoBack() first and fallback to router.replace() to the appropriate tab screen when no navigation history exists. Affected screens: - Listen practice (/practice/listen/[id]) - Read practice (/practice/read/[id]) - Speak conversation (/practice/speak/conversation) - Write practice (/practice/write/[id]) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Summary
Fixes the "The action 'GO_BACK' was not handled by any navigator" error that occurs when clicking the back button in practice screens when there's no navigation history.
Problem
When users navigate directly to a practice screen (e.g., via deep link or direct URL), clicking the back button throws an error because
router.back()fails when there's no previous screen in the navigation stack.Solution
All
router.back()calls now checkrouter.canGoBack()first and fallback torouter.replace()to the appropriate tab screen when no navigation history exists:/(tabs)/listen/(tabs)/read/(tabs)/speak/(tabs)/writeChanges
/practice/listen/[id])/practice/read/[id])/practice/speak/conversation)/practice/write/[id])Test Plan
🤖 Generated with Claude Opus 4.7