-
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
[CRITICAL] Unable to access travel booking flow after accepting terms #45647
Comments
Triggered auto assignment to @zanyrenney ( |
adding external to get eyes on this! |
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil ( |
@rojiphil, @zanyrenney Whoops! This issue is 2 days overdue. Let's get this updated quick! |
bumped the thread about this specific error and asked @stitesExpensify if he heard back from Spotnana. |
@rojiphil, @stitesExpensify, @zanyrenney Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Still investigating this |
any update @stitesExpensify |
Just more slack discussion trying to figure out what's going on here |
This is fixed! |
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: v9.0.8-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): [email protected]
Issue reported by: @kevinksullivan
Slack conversation: https://expensify.slack.com/archives/C05S5EV2JTX/p1721254929395389?thread_ts=1720035711.946819&cid=C05S5EV2JTX
Action Performed:
Expected Result:
Should land in the travel booking flow
Actual Result:
INVALID_REQUEST
Platforms:
Screenshots/Videos
Different screenshots from trials (failed to get this to work ~5 times). Additional screenshots in the slack thread.
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @rojiphilThe text was updated successfully, but these errors were encountered: