-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Travel - Expensify Travel page opens with delay, "Something went wrong" error #46971
Comments
Triggered auto assignment to @AndrewGable ( |
Triggered auto assignment to @puneetlath ( |
👋 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:
|
We think that this bug might be related to #vip-travel |
ProposalPlease re-state the problem that we are trying to solve in this issue.Expensify Travel page opens with delay, "Something went wrong" error What is the root cause of that problem?We don't disable the button and show loading indicator while waiting API response here What changes do you think we should make in order to solve the problem?Add Set Pass
What alternative solutions did you explore? (Optional) |
@shubham1206agra @rushatgabhane @stitesExpensify this deploy blocker was created when executing this PR: #46333 |
Also, @puneetlath @AndrewGable travel is behind a beta, so I think we can demote this as a deploy blocker. |
@rushatgabhane are you taking a look at this? |
@stitesExpensify QA Team still can reproduce the issue bandicam.2024-08-13.12-20-06-953.mp4 |
@stitesExpensify the authCide is being returned. So I'm guessing after clicking book travel multiple times, the final API call was successful Is it possible that the policy has not been provisioned on spotnana? @stitesExpensify sorry im not able to figure out what could be causing this bug. I think we'll have to see the logs |
Based on this I'm thinking that it has something to do with the temporary auth tokens that we use to log in on spotnana. IMO the best solution is to disable the button and show a loading indicator until we get a response from the request so that:
Thoughts @Expensify/design ? |
Hmm. Yeah I don't mind the idea of turning it into a spinner button while it's loading. That being said we can also limit the requests being sent without telling the user or changing the button. I think I'm still leaning towards doing the loading button for this: Keen to hear what the other designers think though |
Yup, I agree with that Jon. |
Same! |
sounds good 👍 Will add a loading state to the button |
@puneetlath, @rushatgabhane, @stitesExpensify Huh... This is 4 days overdue. Who can take care of this? |
How's it going @rushatgabhane? |
@puneetlath @rushatgabhane @stitesExpensify 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! |
we're good to close this. pr on production last month |
@puneetlath payment for C+ review is pending. Can you please reopen and sort payment on upwork? Thanks |
Sorry about that @aimane-chnaif. I've sent you an offer. Please ping me here when you've accepted it. https://www.upwork.com/nx/wm/offer/104357498 |
Accepted thanks |
Paid! |
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: 9.0.17-1
Reproducible in staging?: Y
Reproducible in production?: N
Issue reported by: Applause Internal Team
Issue found when executing PR: #46333
Action Performed:
in Chrome incognito
in Chrome
Expected Result:
Expensify Travel page should open instantly. The "Before we continue..." RHP should close in ND.
Actual Result:
Expensify Travel page opens with a delay of 3-4 seconds. "Something went wrong. Please try again later." error message appears above the "Continue" button after clicking it a few times.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6564343_1723032067955.1.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: