Skip to content

[HOLD for payment 2024-08-29] [$250] Desktop - Onboarding can be skipped by esc key #47189

Closed

Description

@m-natarajan

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: v9.0.18-7
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
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

  1. Launch New Expensify desktop app.
  2. Sign up with a new Gmail account.
  3. During onboarding, press esc key.

Expected Result:

Onboarding cannot be skipped by esc key.

Actual Result:

Onboarding can be skipped by esc key.
This issue only happens on desktop app and not web app.

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

Bug6566750_1723214372806.20240809_223636.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0115ed02f53aa4456b
  • Upwork Job ID: 1822029538491322982
  • Last Price Increase: 2024-08-09
  • Automatic offers:
    • dominictb | Contributor | 103496768
Issue OwnerCurrent Issue Owner: @miljakljajic

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Aug 9, 2024
  2. melvin-bot commented on Aug 9, 2024

    @melvin-bot

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

  3. melvin-bot commented on Aug 9, 2024

    @melvin-bot

    Triggered auto assignment to @miljakljajic (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. github-actions commented on Aug 9, 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.
  5. jasperhuangg commented on Aug 9, 2024

    @jasperhuangg
    Contributor

    Man I almost feel like this should be a feature 😆

    No need to block deploy, onboarding isn't necessary to use the App, and it only happens on desktop.

  6. 42 remaining items

  7. melvin-bot commented on Aug 22, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@allroundexperts] The PR that introduced the bug has been identified. Link to the PR:
    • [@allroundexperts] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@allroundexperts] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@allroundexperts] Determine if we should create a regression test for this bug.
    • [@allroundexperts] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@miljakljajic] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  8. Krishna2323 commented on Aug 28, 2024

    @Krishna2323
    Contributor

    @Krishna2323 Feel free to report the bug yourself in the #expensify-bugs channel and double-check that the person creating the issue assigns you! Thanks for your investigation.

    @allroundexperts, can you please report the other bug in the #expensify-bugs channel and ask the issue creator to assign it to me? I think you should be the C+ there since you have already reviewed this PR and also the solution for the other issue.

  9. jasperhuangg commented on Aug 30, 2024

    @jasperhuangg
    Contributor

    Bump @allroundexperts on above 🙇

  10. allroundexperts commented on Sep 1, 2024

    @allroundexperts
    Contributor

    @jasperhuangg Do you think that the bug reported by @Krishna2323 is worth solving? If so, can you create a new issue and assign both of us?

  11. melvin-bot commented on Sep 2, 2024

    @melvin-bot

    @miljakljajic, @allroundexperts, @jasperhuangg, @dominictb Eep! 4 days overdue now. Issues have feelings too...

  12. jasperhuangg commented on Sep 3, 2024

    @jasperhuangg
    Contributor

    @Krishna2323 Please report the bug yourself via the #expensify-bugs channel. We'll let it go through our standard process.

  13. Krishna2323 commented on Sep 3, 2024

    @Krishna2323
    Contributor

    Thanks. @allroundexperts, could you please do that for me? I don't have access to #expensify-bugs channel.

  14. miljakljajic commented on Sep 3, 2024

    @miljakljajic
    Contributor

    Payment summary:

    @allroundexperts is owed 250 for their work reviewing this PR

  15. miljakljajic commented on Sep 3, 2024

    @miljakljajic
    Contributor

    @dominictb has been paid in upwork

  16. JmillsExpensify commented on Oct 8, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @allroundexperts

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