Skip to content

[$1000] Unexpected error while splitting money- After task history- mobile number #22031

Closed

Description

@kavimuru

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:

Pre-requisite: There must be a task history over user A and user B. Please assign task from User A to User B and send some messages. User B must be a phone number.
1 Login as User A and click on + button and click on split money
2 Set amount and description and select User B
3. Split money and verify if you get error

Expected Result:

There should be no error in splitting money with registered users.

Actual Result:

Got these errors : “There is a previously existing chat between these users.”
“Auth GetEmailByAccountID returned an error” and “Unexpected error requesting money, please try again later”
I got error with both registered and unregistered mobile numbers

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: 1.3.35-5
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

Recording.2288.mp4
reply-kavi.muru.1.mp4

Expensify/Expensify Issue URL:
Issue reported by: @avi-shek-jha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688104145295479

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~016b1c3dd2f7daeaad
  • Upwork Job ID: 1676297367694114816
  • Last Price Increase: 2023-07-25

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Jul 2, 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. added
    InternalRequires API changes or must be handled by Expensify staff
    on Jul 4, 2023
  5. melvin-bot commented on Jul 4, 2023

    @melvin-bot
  6. melvin-bot commented on Jul 4, 2023

    @melvin-bot

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

  7. mallenexpensify commented on Jul 4, 2023

    @mallenexpensify
    Contributor

    Updated OP to make it clear at the beginning that User B needs to be a phone number. I was able to reproduce,
    image

    @abdulrahuman5196 , can you also test to see if you're able to reproduce then propose if this should be internal or external? thx

  8. melvin-bot commented on Jul 7, 2023

    @melvin-bot

    @mallenexpensify, @abdulrahuman5196 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  9. abdulrahuman5196 commented on Jul 7, 2023

    @abdulrahuman5196
    Contributor

    Will check and update in the morning

  10. 79 remaining items

  11. mallenexpensify commented on Sep 11, 2023

    @mallenexpensify
    Contributor
  12. mallenexpensify commented on Sep 21, 2023

    @mallenexpensify
    Contributor
  13. changed the title [-][HOLD #22480] [$1000] Unexpected error while splitting money- After task history- mobile number[/-] [+][$1000] Unexpected error while splitting money- After task history- mobile number[/+] on Oct 4, 2023
  14. mallenexpensify commented on Oct 4, 2023

    @mallenexpensify
    Contributor

    Off hold, @kavimuru can you see if you can still reproduce?
    Thx

  15. mallenexpensify commented on Oct 14, 2023

    @mallenexpensify
    Contributor

    @kavimuru , are you able to reproduce? Thx

  16. kavimuru commented on Oct 16, 2023

    @kavimuru
    Author

    @mallenexpensify I am not able to reproduce

    Recording.1629.mp4
  17. mallenexpensify commented on Oct 17, 2023

    @mallenexpensify
    Contributor

    Closing, unable to reproduce and a lot of shit's changed with split and associated flow.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions