-
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
OpenApp fail/partially fails for Jason's heavy approver account on a throttled connection #47093
Comments
Triggered auto assignment to @francoisl ( |
Triggered auto assignment to @johncschuster ( |
Oh! This is new! Thanks for the SO, Matt! I'll dig into this proper in the AM. |
@francoisl, @johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Sorry I haven't gotten to dive into this yet. I've got it on my plate first thing tomorrow. |
Matt's last update in Slack here mentioned that Eduardo from Callstack started investigating this one, should we co-assign? |
@gedu please could you comment so we can assign you? |
Bumped in Slack 👍 |
Hi, I’m Edu from Callstack, I can take a look at this issue |
Not overdue. This was just assigned. |
@gedu @francoisl @johncschuster this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@gedu how's this going? |
@gedu, @francoisl, @johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not overdue. @gedu is regularly working on this (updates in the PR) |
Not overdue, the PR is still being actively worked on. |
@gedu, @francoisl, @johncschuster Huh... This is 4 days overdue. Who can take care of this? |
Still not overdue. Steady progress is being made in the PR |
Not on hold anymore the dedupe PR was merged |
Thanks, @mountiny! |
@gedu what are the next steps on this one, do we need to de-dupe the OpenApp? |
@gedu, @francoisl, @johncschuster Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@gedu bump on the above! |
We actually merged this PR #50258 which dedupes the OpenApp so we should be better to test this one again soon |
Hey, sorry, I don't think there's a specific fix for this one. There were multiple requests failing and some internal errors. Is it still reproducible? Can we get some steps? |
I think we can close this one and just see if @JmillsExpensify can still experience these issues and start new more precise investigation if so (not sure if there is much to get out of this one) |
Sounds good to me! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number:
Reproducible in staging?: Y
Reproducible in production?: Y
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: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1723132613137659?thread_ts=1722970682.900369&cid=C05LX9D6E07
Action Performed:
Break down in numbered steps
Use an account that approves a lot of reports (@JmillsExpensify's account)
Go to new.expensify.com
Open the Network console and enable 3G throttling
Log in
Expected Result:
Describe what you think should've happened
OpenApp completes successfully and all data is visible in Jason's account
Actual Result:
Describe what actually happened
The app shows a partially loaded state, or nothing is loaded at all
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Using clear cache and restart in the Troubleshoot menu loads the data on a second try
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: