[Medium][$250] Book Travel - Unable to continue setting up travel, error appears

[IuliiaHerets]

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: v9.0.26-4 Reproducible in staging?: Y Reproducible in production?: Y Issue was found when executing this PR: https://github.com/Expensify/App/pull/47809 Issue reported by: Applause Internal Team

Action Performed:

Go to https://staging.new.expensify.com/ Create a brand new account. Green + > Book Travel Enter a company address -> Press Save Press Book Travel -> Accept the terms of service -> Press Continue

Expected Result:

Expensify Travel page opens

Actual Result:

Error appears and Unable to continue setting

Workaround:

Unknown

Platforms:

• [x] Android: Native
• [x] Android: mWeb Chrome
• [x] iOS: Native
• [x] iOS: mWeb Safari
• [x] MacOS: Chrome / Safari
• [x] MacOS: Desktop

Screenshots/Videos

https://github.com/user-attachments/assets/80ecf02c-f920-499c-acbe-926cbaae39a0

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01d6db9f1e6d7f6503
• Upwork Job ID: 1829616128762264680
• Last Price Increase: 2024-08-30

[IuliiaHerets]

We think that this bug might be related to #vip-travel

[melvin-bot[bot]]

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[IuliiaHerets]

@joekaufmanexpensify 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

[Nodebrute]

It's a backend error User is not on Travel Beta

[joekaufmanexpensify]

Can't reproduce, works totally fine for me. Seems like the issue was @IuliiaHerets account is not on the beta.

[joekaufmanexpensify]

Discussing more here

[joekaufmanexpensify]

@IuliiaHerets I got the applause.expensifail.com domain added to the beta. Going to close this for now as I don't think there is a bug here, but please reopen if you're still experiencing an issue after retesting!

[IuliiaHerets]

@joekaufmanexpensify Issue still reproducible. Build - v9.0.26-4, account - applausetester+ihchat4_3008_appa@applause.expensifail.com

https://github.com/user-attachments/assets/50b2cae0-9693-492d-9132-bd76e1764eb4

[joekaufmanexpensify]

@IuliiaHerets can you try again in ~30 minutes? It can sometimes take an hour+ for the beta to take effect.

[IuliiaHerets]

@joekaufmanexpensify QA team noticed that the issue can be reproduced with fresh accounts, after refreshing the page it works well. Build - v9.0.26-5, account - applausetester+ihchat4_3008_123@applause.expensifail.com.

https://github.com/user-attachments/assets/a306c4e4-4e21-4233-8067-3976e1f6cc41

[joekaufmanexpensify]

Ah, yeah. I can reproduce it when I do this with a brand new account. And then no longer can after refreshing. That said, we should still fix this as feels reasonable that some people will try to use travel soon after creating their accounts.

https://github.com/user-attachments/assets/05b574b5-d77a-4b5a-9392-087d9cf5930c

[melvin-bot[bot]]

Job added to Upwork: https://www.upwork.com/jobs/~01d6db9f1e6d7f6503

[melvin-bot[bot]]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (External)

[joekaufmanexpensify]

@Nodebrute are you thinking the issue here is that the beta isn't kicking in for a new account right away or something like that? As i experienced this issue, but my account is on the beta.

[Nodebrute]

@joekaufmanexpensify This was the backend response User is not on Travel Beta. I’ll retest it to confirm.

[Nodebrute]

@joekaufmanexpensify I’m not on the beta, so the response remains the same even after refreshing the page.

[joekaufmanexpensify]

@mananjadhav curious if you agree that this is likely a backend issue?

[joekaufmanexpensify]

Bump @mananjadhav

[mananjadhav]

Sorry I missed this one. I'll check this in a few hours.

[mananjadhav]

@joekaufmanexpensify I am not on beta. I've requested for the access. @joekaufmanexpensify can you confirm if the user is on the beta and you attempted to book travel? What is the API error you see for AcceptSpotnanaTerms.

[joekaufmanexpensify]

@mananjadhav yep, my account is on the beta. Internal logs for it are here.

Error I see is 412 Can't provision Travel for the default workspace.

[joekaufmanexpensify]

Thinking this is an internal bug, but LMK if you disagree

[mananjadhav]

Yeah that looks like an internal bug.

[joekaufmanexpensify]

Searching for a volunteer here.

[joekaufmanexpensify]

Pending volunteer

[joekaufmanexpensify]

Still pending internal volunteer

[joekaufmanexpensify]

Same. This is High in the project, so I expect it will get a volunteer fairly soon

[joekaufmanexpensify]

Same

[joekaufmanexpensify]

Still pending internal volunteer

[melvin-bot[bot]]

@mananjadhav @joekaufmanexpensify 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!

[joekaufmanexpensify]

Still pending internal volunteer. Not too many high issues, so I expect it should get someone soon

[joekaufmanexpensify]

Same

[joekaufmanexpensify]

Same

[joekaufmanexpensify]

Pending internal volunteer

[joekaufmanexpensify]

Same

[joekaufmanexpensify]

Raised in slack again

[joekaufmanexpensify]

Changing to monthly as NewDot travel is not the priority right now.

[joekaufmanexpensify]

Held

[joekaufmanexpensify]

Same