Skip to content

[HOLD for payment 2024-11-14] [$250] Bank account - Website in upper-case letters is accepted despite validation error #52096

Closed

Description

@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: 9.0.58-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh2610001@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Workflows.
  3. Click Connect bank account.
  4. Click Connect manually.
  5. Proceed to "What's your company’s website?".
  6. Enter an invalid website to trigger the error.
  7. Note that the error mentions "Please enter a valid website using lower-case letters.".
  8. Enter a website using upper-case letters.
  9. Click Next.

Expected Result:

App will not proceed to the next page because the error mentions that the website must be in lower-case letters (production behavior).

Actual Result:

App proceeds to the next page when using upper-case letters despite the error.

The error message should be updated if this is the expected behavior.

The same validation message also happens in Invoice company website page.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6656059_1730858126541.20241106_095110.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021854108988948033314
  • Upwork Job ID: 1854108988948033314
  • Last Price Increase: 2024-11-06
  • Automatic offers:
    • suneox | Reviewer | 104768561
    • ahmedGaber93 | Contributor | 104768562
Issue OwnerCurrent Issue Owner: @abekkala

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 6, 2024
  2. melvin-bot commented on Nov 6, 2024

    @melvin-bot

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

  3. melvin-bot commented on Nov 6, 2024

    @melvin-bot

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

  4. melvin-bot commented on Nov 6, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Nov 6, 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.
  6. NJ-2020 commented on Nov 6, 2024

    @NJ-2020
    Contributor

    Offending PR: #51545

    We convert the url to lowercase when checking inside the validation function

    if (values.website && !ValidationUtils.isValidWebsite(Str.sanitizeURL(values.website, CONST.COMPANY_WEBSITE_DEFAULT_SCHEME))) {

    it should be:

    if (values.website && !ValidationUtils.isValidWebsite(values.website)) {
  7. Krishna2323 commented on Nov 6, 2024

    @Krishna2323
    Contributor

    I will raise PR for this, probably in a hour or two.

  8. 29 remaining items

  9. melvin-bot commented on Nov 7, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.58-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-11-14. 🎊

    For reference, here are some details about the assignees on this issue:

  10. melvin-bot commented on Nov 7, 2024

    @melvin-bot

    @suneox / @ahmedGaber93 @abekkala The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  11. changed the title [-][HOLD for payment 2024-11-14] [$250] Bank account - Website in upper-case letters is accepted despite validation error[/-] [+][HOLD for payment 2024-11-18] [HOLD for payment 2024-11-14] [$250] Bank account - Website in upper-case letters is accepted despite validation error[/+] on Nov 11, 2024
  12. melvin-bot commented on Nov 11, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.59-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-11-18. 🎊

    For reference, here are some details about the assignees on this issue:

  13. melvin-bot commented on Nov 11, 2024

    @melvin-bot

    @suneox / @ahmedGaber93 @abekkala The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  14. changed the title [-][HOLD for payment 2024-11-18] [HOLD for payment 2024-11-14] [$250] Bank account - Website in upper-case letters is accepted despite validation error[/-] [+][HOLD for payment 2024-11-14] [$250] Bank account - Website in upper-case letters is accepted despite validation error[/+] on Nov 13, 2024
  15. abekkala commented on Nov 13, 2024

    @abekkala
    Contributor

    @Julesssss & @ahmedGaber93
    I just reviewed the PR - can you confirm that it was @Krishna2323, not @suneox that created the fix?

    To me the payouts appear to be:

    Which differs from the melvin message above

  16. Krishna2323 commented on Nov 13, 2024

    @Krishna2323
    Contributor

    @abekkala, this was a regression, so no payment needed here.

  17. abekkala commented on Nov 13, 2024

    @abekkala
    Contributor

    aaaah ok ok - thanks @Krishna2323

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions