Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.56k stars 2.9k forks source link

[$500] IOU - Application crashes when trying to create IOU on a new account #28196

Closed lanitochka17 closed 1 year ago

lanitochka17 commented 1 year ago

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. Open a New Expensify app
  2. Log in under a new account @applause.expensifail.com
  3. Tap on FAB.
  4. Select Request Money
  5. Enter any amount
  6. Tap the Next button
  7. Select any two members in Split
  8. Tap Add to split

Expected Result:

There should be no program crashes when creating an IOU

Actual Result:

When creating a split bill, it crashes immediately after trying to click on the "Add to split" button

Workaround:

Unknown

Platforms:

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

Version Number: 1.3.74-1

Reproducible in staging?: Yes

Reproducible in production?: No

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

https://github.com/Expensify/App/assets/78819774/ff19eac2-9d79-4022-9600-3148ff012a22

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/~019545d0a73bae509f
  • Upwork Job ID: 1706717835057606656
  • Last Price Increase: 2023-09-26
melvin-bot[bot] commented 1 year ago

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

melvin-bot[bot] commented 1 year ago

Bug0 Triage Checklist (Main S/O)

OSBotify commented 1 year ago

:wave: 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.
melvin-bot[bot] commented 1 year ago

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

chiragsalian commented 1 year ago

I tested on staging on web and it seemed to work fine for me. Can you retest @lanitochka17? Also in your step 2 you mention,

Log in under a new account @applause.expensifail.com

Does it matter to use applause.expensifail.com, asking because i used gmail and it seemed to work fine for me.

namhihi237 commented 1 year ago

Dup #28182

sakluger commented 1 year ago

Asked in the #QA channel in Slack (https://expensify.slack.com/archives/C9YU7BX5M/p1695700402659299)

isagoico commented 1 year ago

Updated the Platforms so they reflect the confirmed reproductions. So far the issue is confirmed to happen in iOS, Android and iOS/Safari.

Also, was able to reproduce the issue in production iOS (both native and mWeb) so we should be good to remove the deploy blocker.

sakluger commented 1 year ago

I removed the deploy blocker and switched to a daily. @chiragsalian do you want to work on this or should we make it external?

chiragsalian commented 1 year ago

external 🙂

melvin-bot[bot] commented 1 year ago

Job added to Upwork: https://www.upwork.com/jobs/~019545d0a73bae509f

melvin-bot[bot] commented 1 year ago

Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

situchan commented 1 year ago

Dupe of https://github.com/Expensify/App/issues/28182 and already fixed

s77rt commented 1 year ago

@sakluger I think we can close this one.

amyevans commented 1 year ago

This was fixed!