Skip to content

[HOLD for payment 2024-05-22] [CRITICAL] [VIP-Travel] Workspace - Unable to select country in Company address #41505

Closed

Description

@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.70-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace settings
  3. Click Company address
  4. Without entering address first, click Country
  5. Select a country

Expected Result:

The country is selected

Actual Result:

The country is not selected. It shows the error "This field is required"

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

Bug6468902_1714658282392.address.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @anmurali

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 2, 2024
  2. melvin-bot commented on May 2, 2024

    @melvin-bot

    Triggered auto assignment to @anmurali (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.

  3. lanitochka17 commented on May 2, 2024

    @lanitochka17
    Author

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

  4. lanitochka17 commented on May 2, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #wave-collect - Release 1

  5. cretadn22 commented on May 2, 2024

    @cretadn22
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    The error message appears upon selecting a country

    What is the root cause of that problem?

    After selecting a country from the country screen, we store this value in route, but fail to update the corresponding field because we don't invoke handleAddressChange.

    What changes do you think we should make in order to solve the problem?

    Within the WorkspaceProfileAddressPage, we need to incorporate logic that automatically updates both the country and state fields upon selection similar to what we implemented in the AddressPage

    const countryFromUrlTemp = route?.params?.country;
    
        // Check if country is valid
        const countryFromUrl = CONST.ALL_COUNTRIES[countryFromUrlTemp as keyof typeof CONST.ALL_COUNTRIES] ? countryFromUrlTemp : '';
        const stateFromUrl = useGeographicalStateFromRoute();
       
        useEffect(() => {
            if (!countryFromUrl) {
                return;
            }
            handleAddressChange(countryFromUrl, 'country');
        }, [countryFromUrl, handleAddressChange]);
    
        useEffect(() => {
            if (!stateFromUrl) {
                return;
            }
            handleAddressChange(stateFromUrl, 'state');
        }, [handleAddressChange, stateFromUrl]);
    
    

    What alternative solutions did you explore? (Optional)

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  6. melvin-bot commented on May 2, 2024

    @melvin-bot

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

  7. github-actions commented on May 2, 2024

    @github-actions
    Contributor

    👋 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.
  8. rlinoz commented on May 2, 2024

    @rlinoz
    Contributor

    This is related to a new feature coming from this PR #38381

    cc: @smelaa @shubham1206agra

  9. 32 remaining items

  10. rlinoz commented on May 21, 2024

    @rlinoz
    Contributor

    @s77rt reviewed the PR

  11. melvin-bot commented on May 22, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    • ROLE: @s77rt paid $(AMOUNT) via Upwork (LINK)
    • Contributor: @smelaa is from an agency-contributor and not due payment

    BugZero Checklist (@anmurali)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  12. melvin-bot commented on May 27, 2024

    @melvin-bot

    @rlinoz, @anmurali, @s77rt, @smelaa Eep! 4 days overdue now. Issues have feelings too...

  13. rlinoz commented on May 28, 2024

    @rlinoz
    Contributor

    friendly bump @anmurali

  14. melvin-bot commented on May 31, 2024

    @melvin-bot

    @rlinoz, @anmurali, @s77rt, @smelaa 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  15. anmurali commented on Jun 4, 2024

    @anmurali

    @s77rt - offer is here

  16. s77rt commented on Jun 4, 2024

    @s77rt
    Member

    @anmurali Accepted! Thanks!

  17. melvin-bot commented on Jun 7, 2024

    @melvin-bot

    @rlinoz, @anmurali, @s77rt, @smelaa Whoops! This issue is 2 days overdue. Let's get this updated quick!

  18. melvin-bot commented on Jun 11, 2024

    @melvin-bot

    @rlinoz, @anmurali, @s77rt, @smelaa Still overdue 6 days?! Let's take care of this!

  19. anmurali commented on Jun 11, 2024

    @anmurali

    Paid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions