Skip to content

[HOLD for payment 2023-08-21] [HOLD for #23481] [$1000] mWeb - Sign out - Button hidden under bottom, hard to sign out #20709

Closed

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. launch App and login
  2. Tap on profile > Settings
  3. Tap on Sign Out

Expected Result:

Sign out button should be visible.

Actual Result:

Button hidden under bottom, hard to sign out

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.27.2

Reproducible in staging?: yes

Reproducible in production?: yes

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6091719_RPReplay_Final1686681051.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01f559d55619af61e2
  • Upwork Job ID: 1675953147854782464
  • Last Price Increase: 2023-07-19

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 13, 2023
  2. melvin-bot commented on Jun 13, 2023

    @melvin-bot

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

  3. melvin-bot commented on Jun 13, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. kevinksullivan commented on Jun 14, 2023

    @kevinksullivan
    Contributor
  5. melvin-bot commented on Jun 19, 2023

    @melvin-bot

    @kevinksullivan Eep! 4 days overdue now. Issues have feelings too...

  6. kevinksullivan commented on Jun 20, 2023

    @kevinksullivan
    Contributor

    bumping slack thread and closing for now

  7. kbecciv commented on Jul 2, 2023

    @kbecciv
    Author

    Hello @kevinksullivan I'm reopening the issue, because one of the contributor has the same issue with hidden buttons around the app.
    Here is the Slack conversation https://expensify.slack.com/archives/C049HHMV9SM/p1686663005982659

    photo_2023-06-13 18 30 47

    IMG_1109.1.MP4
    IMG_1109.MP4
  8. reopened this on Jul 2, 2023
  9. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 3, 2023
  10. 123 remaining items

  11. kevinksullivan commented on Aug 17, 2023

    @kevinksullivan
    Contributor

    @s77rt do you get paid in NewDot?

  12. s77rt commented on Aug 17, 2023

    @s77rt
    Member

    @kevinksullivan No, still in Upwork

  13. sakluger commented on Aug 21, 2023

    @sakluger
    Contributor

    @kevinksullivan are you back and able to handle this one? Or would you like me to handle it?

    @jscardona12 regarding your comment on payment, can you clarify where there was a $2000 bounty? This issue shows $1000 so I'm not sure what you're referring to.

  14. kevinksullivan commented on Aug 21, 2023

    @kevinksullivan
    Contributor

    I can do it @sakluger . Still waiting on @jscardona12 's response though.

  15. jscardona12 commented on Aug 22, 2023

    @jscardona12
    Contributor

    Hi, what I was saying was in a point the regression bounty was 2000 dollars.
    Not the original ones. I was wondering if since we reapply a previous fix, that ended up in regression and to be honest the ton of testing and research to find a viable solution if it would be possible to pay 1000.

    Thx!

    Cc: @kevinksullivan

  16. sakluger commented on Aug 23, 2023

    @sakluger
    Contributor

    I don't see anywhere that the bounty was $2000 - we pay out for this issue based on the price of this issue. We appreciate all your work on this, and testing and research is expected to be included in the job price.

  17. sakluger commented on Aug 24, 2023

    @sakluger
    Contributor

    @kevinksullivan I'm going to remove my assignment now, let me know if you need my help with anything else here!

  18. removed their assignment
    on Aug 24, 2023
  19. kevinksullivan commented on Aug 24, 2023

    @kevinksullivan
    Contributor
  20. kevinksullivan commented on Aug 24, 2023

    @kevinksullivan
    Contributor

    Payments made for $500 due to merge delay.

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