Skip to content

[PAY 8/13] Request Money / Split Money Greater than or equal to 100,000,000 InDefinite Loading #4130

Closed

Description

@Santhosh-Sellavel

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. Create a new Request Money / Split
  2. Enter Amount 100,000,000

Expected Result:

Case 1: If there is an upper Request limit, the user should be notified with an error message.
Case 2: No upper limit means the request should have been sent successfully.

Actual Result:

Indefinite loading

Request Money:

Screen.Recording.2021-07-17.at.8.22.30.PM.mov

Split:
Screenshot 2021-07-17 at 8 25 41 PM

Workaround:

Request amount less than 100,000,000. Even 99,999,999 works.

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Proposal

Need inputs from the Expensify team, this might be a back-end issue if there is no upper limit.

But I propose proper error handling should be done for situations like this. If a request fails based on request type we need to show appropriate messages to the user.

Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:

View all open jobs on Upwork

Activity

  1. MelvinBot commented on Jul 17, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @bfitzexpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

  2. removed
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Jul 17, 2021
  3. removed their assignment
    on Jul 20, 2021
  4. MelvinBot commented on Jul 20, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  5. thienlnam commented on Jul 21, 2021

    @thienlnam
    Contributor

    In the video you put in the description, it looks like we're actually getting a response back of invalid amount so it seems like this is handled in the back-end but just needs some front-end handling for when we get that error message

  6. thienlnam commented on Jul 21, 2021

    @thienlnam
    Contributor

    Luckily, my friends only owe me 99 million instead of 100 million :trollface:

  7. Santhosh-Sellavel commented on Jul 22, 2021

    @Santhosh-Sellavel
    CollaboratorAuthor

    In the video you put in the description, it looks like we're actually getting a response back of invalid amount so it seems like this is handled in the back-end but just needs some front-end handling for when we get that error message

    If I request in Rupees ₹100,000,000, Request fails.

    But If request in pound £10,000,000, Request success.

    Now User Owes more than ₹1,000,000,000.

    100 Million rupees is invalid if I ask in rupees.
    But I can ask 1 billion rupees if asked in £ pound.

    Screenshot_20210722-124946_Expensifycash.jpg

    @thienlnam

  8. thienlnam commented on Jul 26, 2021

    @thienlnam
    Contributor

    Interesting, are the responses the same on all the failed transactions?

  9. Santhosh-Sellavel commented on Jul 27, 2021

    @Santhosh-Sellavel
    CollaboratorAuthor

    @thienlnam Following are responses for failed transactions
    Request Money :
    {"jsonCode":405,"message":"405 invalid amount","requestID":"-------SOMEID-------"}

    Split Bill:
    {"jsonCode":404,"message":"404 Splits amount does not equal total amount","requestID":"-------SOMEID-----"}

  10. thienlnam commented on Jul 27, 2021

    @thienlnam
    Contributor

    Thanks @Santhosh-Sellavel, I think the most straightforward solution here is to catch those errors and show some kind of error message / cancel the transaction so the user doesn't sit on an infinite spinner

  11. 24 remaining items

  12. mallenexpensify commented on Aug 5, 2021

    @mallenexpensify
    Contributor

    https://www.upwork.com/jobs/~0186df8dda363f929c
    @Santhosh-Sellavel , can you please 'submit a proposal'/apply in Upwork and I'll hire you there? Please confirm here once you do.

  13. Santhosh-Sellavel commented on Aug 5, 2021

    @Santhosh-Sellavel
    CollaboratorAuthor

    https://www.upwork.com/jobs/~0186df8dda363f929c
    @Santhosh-Sellavel , can you please 'submit a proposal'/apply in Upwork and I'll hire you there? Please confirm here once you do.

    Done @mallenexpensify

  14. mallenexpensify commented on Aug 5, 2021

    @mallenexpensify
    Contributor

    Hired @Santhosh-Sellavel in Upwork!

  15. thienlnam commented on Aug 9, 2021

    @thienlnam
    Contributor

    PR is staging checklist, changes have been merged

  16. mallenexpensify commented on Aug 9, 2021

    @mallenexpensify
    Contributor

    Per the PR, deployed to staging two days ago, I'll issue payment on Friday if there are no regressions

  17. changed the title [-]Request Money / Split Money Greater than or equal to 100,000,000 InDefinite Loading[/-] [+][PAY 8/13] Request Money / Split Money Greater than or equal to 100,000,000 InDefinite Loading[/+] on Aug 9, 2021
  18. Santhosh-Sellavel commented on Aug 16, 2021

    @Santhosh-Sellavel
    CollaboratorAuthor

    Are there any regressions, can we close this?
    @mallenexpensify

  19. mallenexpensify commented on Aug 16, 2021

    @mallenexpensify
    Contributor

    Paid @Santhosh-Sellavel with bonus for reporting the issue. Code has been on production for 5 days without a regression, closing now (not sure why it didn't auto-close before)

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

Metadata

Metadata

Labels

EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions