-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2024-04-05] Expense - Expense preview shows skeleton loading after paying with Expensify #38869
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Triggered auto assignment to @luacmartins ( |
@luacmartins FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #wave-collect - Release 1 |
Looking at this one now |
This is caused by calling |
Discussing here - https://expensify.slack.com/archives/C01GTK53T8Q/p1711394667108379 |
I'm not able to reproduce, but for an unrelated reason. I'm not able to get past the Expense report submission in a collect workspace. Going to try with fresh accounts + a free workspace |
I'm still struggling with this one - I reproduced it once but am running into two unrelated issues, reported here |
I've added a test bank account and was wondering, can we use it to make payments? I'm pretty sure the issue might be in @lanitochka17, could you help us out by sharing some logs? If you could add |
Hmm I was trying to get the logs asked above, but I can't reproduce the issue right now. Gonna keep trying. |
Ok, managed to reproduce again. Here are the logs @perunt
|
You could, but you'd have funds debited from it, but as long as you're paying me I'm cool with that 😄
Yes, that's where I've traced it down to as well. I'm not too sure what's wrong with it yet, but maybe the logs above might help. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.57-5 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 2024-04-05. 🎊 |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
This is done! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.56-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: around Reproducible in production?:
Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Expected Result:
In Step 5, after clicking Pay with Expensify, the page will not be blank or show skeleton loading
Actual Result:
In Step 5, after clicking Pay with Expensify, the page shows skeleton loading above the "settling up" message
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6423773_1711143706448.20240323_053656.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: