Skip to content

Unable to delete a contact method including capital letters #19080

Closed

Description

@trjExpensify

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 the app -> Login in account
  2. Navigate to Avatar > Profile > contact method
  3. Add a new contact email including capital letters i.e DERP@DERP.COM
  4. Delete the contact method you just added

Expected Result:

You should be able to delete the contact method

Actual Result:

Attempting to delete the contact method results in this error: Auth DeleteLogin returned an error

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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: v1.3.14-14
Reproducible in staging?: Y
Reproducible in production?: Y
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

Screen_Recording_20230509_000311_New.Expensify.mp4

Expensify/Expensify Issue URL:
Issue reported by: @dhairyasenjaliya
Slack conversation: #18301 (comment)

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01c866a623249c0072
  • Upwork Job ID: 1658592013696098304
  • Last Price Increase: 2023-05-16

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 16, 2023
  2. melvin-bot commented on May 16, 2023

    @melvin-bot

    Current assignee @Beamanator is eligible for the Engineering assigner, not assigning anyone new.

  3. melvin-bot commented on May 16, 2023

    @melvin-bot

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

  4. melvin-bot commented on May 16, 2023

    @melvin-bot
  5. melvin-bot commented on May 16, 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
  6. melvin-bot commented on May 16, 2023

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @rushatgabhane (Internal)

  7. 33 remaining items

  8. trjExpensify commented on May 30, 2023

    @trjExpensify
    ContributorAuthor

    Okay, but same same.. are you saying the regression test update or that has been accounted for?

  9. Beamanator commented on May 31, 2023

    @Beamanator
    Contributor

    Oh oh like do I think we should add something to the regression tests for this? I think yes! We definitely don't want to be able to add mixed-case logins (primary or secondary) anywhere at the moment 👍

  10. trjExpensify commented on Jun 2, 2023

    @trjExpensify
    ContributorAuthor

    Kewl, so can yah do this step or have you somewhere else? (I see it checked off).

    @Beamanator] 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.

  11. Beamanator commented on Jun 2, 2023

    @Beamanator
    Contributor

    Oh ya sure, sorry I thought the steps would be pretty obvious :D I'm thinking something like:

    1. Add a new contact method with some uppercase and some lowercase letters (example: MYEMAIL@gmail.COM)
    2. Verify the contact method gets added in the "Contact Methods" page, in all lowercase letters (myemail@gmail.com)
    3. Try removing that newly added contact method
    4. Verify everything works as intended
  12. added and removed on Jun 5, 2023
  13. trjExpensify commented on Jun 7, 2023

    @trjExpensify
    ContributorAuthor

    Great, amended a touch and created the issue for Applause.

    Presuming as well with the Web-E issue merged and on prod we can close. Reopen if I missed something!

  14. dhairyasenjaliya commented on Jun 7, 2023

    @dhairyasenjaliya
    Contributor

    Hey @trjExpensify am im eligible for reporting this bug 🐛

  15. trjExpensify commented on Jun 7, 2023

    @trjExpensify
    ContributorAuthor

    Ah, sorry man. @Beamanator throwing me off! 😆

    FYI there was no payment needed, it was resolved internally

    Sent you a contract on this job.

  16. Beamanator commented on Jun 7, 2023

    @Beamanator
    Contributor

    Oh shit that's totally my bad 🙃

  17. dhairyasenjaliya commented on Jun 8, 2023

    @dhairyasenjaliya
    Contributor

    no issue 😅

  18. trjExpensify commented on Jun 8, 2023

    @trjExpensify
    ContributorAuthor

    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.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions