You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No specific action – just any action that causes an uncaught JS exception caught by our ErrorBoundary. Of course, we never want to land here, because it's a sign that our app isn't working as it's supposed to. But over the lifetime of this app it's a near-inevitability that we'll introduce a few bugs that get caught by our error boundary. Right now, we just display a blank white screen.
@roryabraham and whomever might be assigned as the CM, I added @zoontek as "Reported by:" in the OP because I think they should be compensated $250 for reporting this here, once this issue has been fixed internally or externally
This is similar to a 404, but not exactly the same. 404 means the user tried to go to a page that doesn't exist (and that concept doesn't really exist on a mobile app). This is more of a 500 error page which means the user didn't do anything wrong, and the error happened on our side. Basically, this page would be shown when we have a bug in the application that would normally crash the app, but instead we'll catch that error and show them this page.
Also, a small note to add to Rory's comment (in case it helps in the decision)
Refresh logic was curated based on combined efforts from multiple persons after Manan asked for help #6856 (comment) (point 4) till #6856 (comment).
@roryabraham, and I'd like to take back the request as I've been also assigned #7037 which is a relatively small PR, so I feel that the budget increase wouldn't be required and the effort will be adjusted there.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.30-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Alright! @parasharrajat I paid you for the C+ in Upwork (our documentation says to pay C+ the same amount as the hired contractor which is $250 for this job). This is my first time paying for C+ so let me know if that's not correct or if I missed something. Thanks!
Activity
MelvinBot commentedon Nov 30, 2021
Triggered auto assignment to @megankelso (
Design), see these Stack Overflow questions for more details.megankelso commentedon Dec 3, 2021
rosegrech commentedon Dec 3, 2021
mallenexpensify commentedon Dec 4, 2021
@roryabraham and whomever might be assigned as the CM, I added @zoontek as "Reported by:" in the OP because I think they should be compensated $250 for reporting this here, once this issue has been fixed internally or externally
megankelso commentedon Dec 6, 2021
rosegrech commentedon Dec 6, 2021
roryabraham commentedon Dec 6, 2021
roryabraham commentedon Dec 6, 2021
This is similar to a
404, but not exactly the same.404means the user tried to go to a page that doesn't exist (and that concept doesn't really exist on a mobile app). This is more of a500error page which means the user didn't do anything wrong, and the error happened on our side. Basically, this page would be shown when we have a bug in the application that would normally crash the app, but instead we'll catch that error and show them this page.megankelso commentedon Dec 6, 2021
MelvinBot commentedon Dec 6, 2021
Triggered auto assignment to @gabrielessner (
Waiting for copy), see https://stackoverflow.com/c/expensify/questions/7025/ for more details.82 remaining items
parasharrajat commentedon Jan 14, 2022
Also, a small note to add to Rory's comment (in case it helps in the decision)
Refresh logic was curated based on combined efforts from multiple persons after Manan asked for help #6856 (comment) (point 4) till #6856 (comment).
mananjadhav commentedon Jan 14, 2022
@roryabraham, and I'd like to take back the request as I've been also assigned #7037 which is a relatively small PR, so I feel that the budget increase wouldn't be required and the effort will be adjusted there.
roryabraham commentedon Jan 14, 2022
Okay, glad that easier issue makes up for it.
botify commentedon Jan 18, 2022
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.30-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2022-01-25. 🎊
[-]Create Expensify branded generic error page[/-][+][HOLD for payment 2022-01-25] Create Expensify branded generic error page[/+]Christinadobrzyn commentedon Jan 27, 2022
No regressions on this PR - paid @mananjadhav in Upwork - closing job in Upwork and this issue.
parasharrajat commentedon Jan 27, 2022
@Christinadobrzyn Where can I apply for C+, job is closed?
Christinadobrzyn commentedon Jan 27, 2022
Ah so sorry @parasharrajat! Let me reopen the job and hire you for it!
Christinadobrzyn commentedon Jan 27, 2022
Alright! @parasharrajat I paid you for the C+ in Upwork (our documentation says to pay C+ the same amount as the hired contractor which is $250 for this job). This is my first time paying for C+ so let me know if that's not correct or if I missed something. Thanks!
parasharrajat commentedon Jan 27, 2022
That's correct. Thanks, @Christinadobrzyn.
nyomanjyotisa commentedon Nov 18, 2026
The generic error page added in #6856 styled its title as a heading without exposing a heading role. Tracked in #107208 and fixed in #105224.