Skip to content

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

@izarutskaya

Description

@izarutskaya

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com 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

Bug6395107_1709099549215!capture

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions