[$500] Tag - "no longer valid" initially appears for Tag when request with a valid tag is created

[lanitochka17]

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.28-0
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: Applause - Internal Team
Slack conversation:

Action Performed:

Precondition:

• User is an employee of Collect workspace on Old Dot which has tags

1. Go to workspace chat and open manual request page
2. Enter amount > Next > Show more
3. Click Tag and select a tag
4. Create the request
5. Immediately open request details page
6. Return to expense report and go to request details page again

Expected Result:

Since the selected tag is existing and valid, "no longer valid" will not appear on Tag row

Actual Result:

"no longer valid" appears on Tag row when the request details page is visited immediately after requesting it. It disappears when revisiting the page

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6347698_1705675090612.20240119_003524.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~014d7530b698dd531e
• Upwork Job ID: 1748356015802679296
• Last Price Increase: 2024-01-19

[melvin-bot]

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~014d7530b698dd531e

[melvin-bot]

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

[lanitochka17]

#wave6-collect-submitters

[cead22]

I think there was a network request that failed in there, notice how the compose box is gone in the screenshot. Also, being able to selected a tag that isn't in the policy means you don't have the updated tags on the client, so we're either not sending the update, or the network failed there too. Can this be reproduced reliably?

[miljakljajic]

@lanitochka17 is this still reproducible for you? I tried but I wasn't able to get up a tag list even though the collect workspace had tags on it. I was working in staging. Can anyone provide some more detail in the repro steps? (sorry!)

[lanitochka17]

@miljakljajic Hello
Still reproducible on v1.4.31-4
Immediately open request details page

20240125_031829.mp4

[cead22]

It looks like going into the thread failed again, and I'm pretty sure it's the same issue as this one #33114, which will be fixed as part of this issue #31411, so closing