-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Added an Error Page #6856
Added an Error Page #6856
Conversation
@roryabraham @parasharrajat While most of the work is done, I need help with the following to close this. Can you please help?
|
cc: @Expensify/design
Web => location.reload.
I think the best would be to mark it as No QA. |
may be utilized react-navigation for this. Reset the navigation state and redirect the user to the home Route. |
I guess the requirement is to reload on the same route and not home route. I'll check what are the options. |
Then you can redirect to the same route just reset the state. |
I've picked the current route by adding a function. Is that the right direction? |
Looks pretty good to me, but looping in @megankelso since she worked on the designs for this. |
Minor piece of feedback for @mananjadhav – when you address feedback, feel free to resolve the reviewer's comment threads to make it easier for other reviewers to scan the issue and pick out any threads with active discussion. |
Noted @roryabraham. I generally used to put a 👍 emoji on completion. Will resolve next time PR onwards. |
@roryabraham @parasharrajat I've tried finding a Can we use |
I agree we shouldn't rely on
|
Missed that. Yeah we can use it. |
I've asked in the slack channel, but still went ahead to test the lib. It seems to work fine. Will change if I get any feedback to not use lib, |
…into feat/error-page
9209388
@roryabraham PR updated. Left with two comments - punctuation utility and button size prop. |
…rror-page # Conflicts: # src/styles/styles.js
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.
Other than the one remaining thread I think this looks good.
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @roryabraham in version: 1.1.29-6 🚀
|
@mananjadhav @roryabraham @shawnborton @parasharrajat |
Ah, sorry this PR title should have been prefixed with ...unless... we could purposely introduce such a bug to QA this, then revert that PR 😈 |
I have a suggestion. Just try to run the QA for this on any crash issue. I think there is one for room details. |
Have a link? |
Thanks @parasharrajat, that's perfect! @mvtglobally for QA steps: Web/Desktop/mWeb
iOS/Android
|
Thank you @parasharrajat @roryabraham for helping with this. |
@roryabraham @mananjadhav Upload.from.GitHub.for.iOS.MOV |
Also On IOS the page doesn't really display as app crashes. Expected? https://user-images.githubusercontent.com/43995119/149956996-295be13f-1109-499b-afba-8bb9c435411b.MOV |
I saw the video for iOS, it seems ti flashes for a second and then crashes. It shouldn't be related to the ErrorPage, but yeah let @roryabraham and @parasharrajat comment. |
It seems that the error was thrown out of the Render tree and yeah that won't be caught by the current implementation. Should that be part of this issue? |
@roryabraham Should we log a new issue or just leave it as is |
@mvtglobally That's a separate issue, the scope of this PR was really just designing and implementing a generic error page. As long as the page displays correctly, I think other issues are out-of-scope. From what I can see in the videos, this looks to me like it's passing QA. I'm going to check it off on the checklist. |
🚀 Deployed to production by @roryabraham in version: 1.1.30-3 🚀
|
Details
Fixed Issues
$ #6552
Tests
QA Steps
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android