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
{{ message }}
Repository navigation
[$500] Desktop - Reload - ''Hmm... it's not here'' when reloading the desktop app #31592
Version Number: 1.4.1-5 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: Applause - Internal Team Slack conversation:
Action Performed:
Launch the desktop app
Press Cmd + R or click on the View menu, then select ''Reload''
Expected Result:
No errors should be encountered when reloading the app
Actual Result:
When reloading the app, a 'page not found' error is displayed
Hmm... it's not here
Oops, this page cannot be found
Go back to home page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]Desktop - Reload - ''Hmm... it's not here'' when reloading the desktop app[/-][+][$500] Desktop - Reload - ''Hmm... it's not here'' when reloading the desktop app[/+]on Nov 21, 2023
Been working on a similar issue for weeks that might be related. I'm also getting the 'hmm' error after every time I've updated the app the past two days. #28495
This seems to be a dupe of #28495 and given the video@s77rt shared, it seems like a race condition that was made worse with the last deploy. I'm gonna remove the deploy blocker label since this is already happening in previous versions, just not as noticeable. We need to keep investigating and fix this though.
Activity
melvin-bot commentedon Nov 20, 2023
Triggered auto assignment to @deetergp (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.lanitochka17 commentedon Nov 20, 2023
Production:
Screen.Recording.2023-11-20.at.19.21.05.mov
luacmartins commentedon Nov 20, 2023
I can reproduce this and see the following logs. It seems like we're intentionally navigating to that page.
[-]Desktop - Reload - ''Hmm... it's not here'' when reloading the desktop app[/-][+][$500] Desktop - Reload - ''Hmm... it's not here'' when reloading the desktop app[/+]melvin-bot commentedon Nov 21, 2023
Job added to Upwork: https://www.upwork.com/jobs/~01fc65658e91d3dd1c
melvin-bot commentedon Nov 21, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (
External)erquhart commentedon Nov 21, 2023
Likely same root cause as #28495, may be a dupe.
tienifr commentedon Nov 21, 2023
I posted a proposal on the other issue, it will fix this one as well
6 remaining items
situchan commentedon Nov 21, 2023
So I can conclude that @tienifr's solution is just workaround without fixing the root cause.
We should really find out the offending PR.
s77rt commentedon Nov 21, 2023
This may be a dupe. I think this issue existed for a while but due to another factor the bug is constantly reproducible now.
I tested this on v1.3.83-0. The bug is there but not very easy to reproduce
Screen.Recording.2023-11-21.at.6.13.29.PM.mov
mallenexpensify commentedon Nov 21, 2023
Been working on a similar issue for weeks that might be related. I'm also getting the 'hmm' error after every time I've updated the app the past two days.
#28495
mallenexpensify commentedon Nov 21, 2023
From Tim G in this internal thread, in case it's helpful:
The bulk of that logic is here: https://github.com/Expensify/App/blob/main/src/libs/ReportUtils.js#L596-L631
s77rt commentedon Nov 21, 2023
@tienifr Any idea why is the initial url
app://-Can we change it?luacmartins commentedon Nov 21, 2023
This seems to be a dupe of #28495 and given the video @s77rt shared, it seems like a race condition that was made worse with the last deploy. I'm gonna remove the deploy blocker label since this is already happening in previous versions, just not as noticeable. We need to keep investigating and fix this though.
s77rt commentedon Nov 24, 2023
@luacmartins Shouldn't we close this one?
luacmartins commentedon Nov 24, 2023
Yea, we should be good to close.