[$500] Settings - The classicRedirect->dismissedReason displays the first response

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Found when executing PR : #34925

Version Number: 1.4.44.0
Reproducible in staging?: Y
Reproducible in production?: N, new feature
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal Team

Action Performed:

1. Complete steps 1 to 17 for any option (Mandatory exit survey for users going back to OldDot #34925
   )
2. Complete steps 1 to 17 for another option, make sure to choose a different reason

Expected Result:

It should always display the actual response.

Actual Result:

The classicRedirect->dismissedReason displays the first response.

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0187eb3870fabaaf97
• Upwork Job ID: 1762800266729877504
• Last Price Increase: 2024-02-28

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0187eb3870fabaaf97

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @grgia (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[izarutskaya]

We think that this bug might be related to #wave9-collect-signup
CC @MitchExpensify

[grgia]

@roryabraham this is from your PR

[roryabraham]

Weird. I bet this is actually a problem in Web-E. I'm guessing what happened here is that the response that was sent the 2nd time was rejected by the firewall for some reason. I had seen that but thought I fixed it

[melvin-bot]

Current assignee @DylanDylann is eligible for the Internal assigner, not assigning anyone new.

[roryabraham]

@AndrewGable fixed this in https://github.com/Expensify/Web-Expensify/pull/41146. Cheers!