-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Fix crashes when personal details are not available #9385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
dbd8656
Fix crash when personalDetails are missing
aldo-expensify 07e0997
Show spinner when personal details are not available
aldo-expensify dea9de5
Merge branch 'aldo_test-proposed-solution' of github.com:Expensify/Ap…
aldo-expensify c379cc6
Fix import
aldo-expensify d47836b
Add isRequired to personalDetails prop
aldo-expensify 7b1660c
Remove unnecessary check
aldo-expensify bb05c28
Find personal details when creating new chat
aldo-expensify dd87f7e
Merge branch 'main' of github.com:Expensify/App into aldo_fix-crash-m…
aldo-expensify 1cc5eea
Replace ActivityIndicator by FullscreenLoadingIndicator
aldo-expensify File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this line is probably what is causing this crash: #9545
It doesn't seem like a very safe way to access properties. It appears like there can be cases where
props.route.paramsisundefined. Is that a valid case? Should this uselodashGetinstead?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you are right. If you just open
https://new.expensify.com/detailswithout the paramlogin, it crashes. I'll spin a small PR to fix it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, this feels low priority, I don't know how a user ended up with the URL without the parameter.