Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HOLD for payment 2023-10-30] [HOLD #25714] Split bill - App crashes when splitting bill in group with both expensifail and gmail accounts #21268

Closed
3 of 6 tasks
lanitochka17 opened this issue Jun 21, 2023 · 23 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Engineering

Comments

@lanitochka17
Copy link

lanitochka17 commented Jun 21, 2023

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


Issue found when executing PR #20838

Action Performed:

  1. Login to NewDot
  2. Create a group with several gmail and expensifail accounts
  3. Go to created group chat
  4. Tap + and create a split bill for the whole group

Expected Result:

Successful Split Bill

Actual Result:

App crashes (Android)
App freezes (Web, mWeb)
Error message when creating split bill (iOS)

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.30.0

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

video_13.mp4
Pronin.crash.2106.1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

@lanitochka17 lanitochka17 added the DeployBlockerCash This issue or pull request should block deployment label Jun 21, 2023
@OSBotify
Copy link
Contributor

👋 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
Copy link

melvin-bot bot commented Jun 21, 2023

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

@luacmartins
Copy link
Contributor

@aldo-expensify if it helps, I see these logs in crashlytics:

Non-fatal Exception: io.invertase.firebase.crashlytics.JavaScriptError: array list[1] is not type String
       at .stringListFromIterable(address at index.android.bundle:1:5688527)
       at .anonymous(address at index.android.bundle:1:5690123)
       at .arrayToString(address at index.android.bundle:1:1847665)
       at .createSplitsAndOnyxData(address at index.android.bundle:1:2878809)
       at .splitBill(address at index.android.bundle:1:2881501)
       at .anonymous(address at index.android.bundle:1:2671772)
       at .onConfirm(address at index.android.bundle:1:2672957)
       at .anonymous(address at index.android.bundle:1:2767405)
       at .onPress(address at index.android.bundle:1:2767806)
       at .onPress(address at index.android.bundle:1:2770537)
       at .onPress(address at index.android.bundle:1:1725618)
       at .anonymous(address at index.android.bundle:1:1839331)
       at ._performTransitionSideEffects(address at index.android.bundle:1:416247)
       at ._receiveSignal(address at index.android.bundle:1:415835)
       at .onResponderRelease(address at index.android.bundle:1:414649)
       at .apply((native):0:0)
       at .invokeGuardedCallbackImpl(address at index.android.bundle:1:337841)
       at .apply((native):0:0)
       at .invokeGuardedCallback(address at index.android.bundle:1:337898)
       at .apply((native):0:0)
       at .invokeGuardedCallbackAndCatchFirstError(address at index.android.bundle:1:337930)
       at .executeDispatch(address at index.android.bundle:1:338062)
       at .executeDispatchesAndReleaseTopLevel(address at index.android.bundle:1:342319)
       at .forEach((native):0:0)
       at .forEachAccumulated(address at index.android.bundle:1:339560)
       at .anonymous(address at index.android.bundle:1:342671)
       at .batchedUpdatesImpl(address at index.android.bundle:1:401877)
       at .batchedUpdates(address at index.android.bundle:1:342239)
       at ._receiveRootNodeIDEvent(address at index.android.bundle:1:342512)
       at .receiveTouches(address at index.android.bundle:1:396657)
       at .apply((native):0:0)
       at .__callFunction(address at index.android.bundle:1:139406)
       at .anonymous(address at index.android.bundle:1:137771)
       at .__guard(address at index.android.bundle:1:138724)
       at .callFunctionReturnFlushedQueue(address at index.android.bundle:1:137729)

@aldo-expensify
Copy link
Contributor

I got this on web:

image

The error looks similar to the one above.

@aldo-expensify
Copy link
Contributor

aldo-expensify commented Jun 21, 2023

The gmail participants of the group have login: undefined:

image

I find it strange because these are accounts that existed in my database (I created them before creating the group)

The code crashes around here:

const formattedParticipants = Localize.arrayToString([currentUserLogin, ..._.map(participants, (participant) => participant.login)]);

These accounts have missing the login in the OpenApp response:

image

I think that's because I didn't have chats between these accounts before creating the group.

@aldo-expensify
Copy link
Contributor

Asking in slack about expected behaviour: https://expensify.slack.com/archives/C03TQ48KC/p1687387011143229

@aldo-expensify
Copy link
Contributor

Considering this, this is not a deploy blocker anymore.

@aldo-expensify aldo-expensify added Daily KSv2 Hourly KSv2 and removed Hourly KSv2 DeployBlockerCash This issue or pull request should block deployment labels Jun 21, 2023
@aldo-expensify
Copy link
Contributor

I created a draft PR with the progress I was able to make to disallow splitting with accounts that have a missing login. Since less accounts are selected than the total of the group, this ends up creating a sub group with only the selected accounts of the split. See the result in the video here: #21290

I will prioritize other things for now since this is not for SNH anymore.

cc @Beamanator @puneetlath feel free to continue working on this if you want, I won't remove my assignment for now.

@aldo-expensify
Copy link
Contributor

@puneetlath @Beamanator I haven't been able to get back to this, and I'm going OOO for the next week. I'll reassign it to @puneetlath since you offered yourself before :)

@puneetlath
Copy link
Contributor

I will pick this back up soon.

@puneetlath
Copy link
Contributor

Still on hold.

@melvin-bot melvin-bot bot removed the Overdue label Sep 7, 2023
@Julesssss
Copy link
Contributor

Reproduced on Android native and iOS native today: 1.3.67-3

@melvin-bot melvin-bot bot added the Overdue label Sep 15, 2023
@puneetlath
Copy link
Contributor

#25714 is getting close.

@melvin-bot melvin-bot bot removed the Overdue label Sep 18, 2023
@melvin-bot melvin-bot bot added the Overdue label Sep 27, 2023
@puneetlath
Copy link
Contributor

Seems to be fixed now!

@melvin-bot melvin-bot bot removed the Overdue label Oct 4, 2023
@izarutskaya
Copy link

izarutskaya commented Oct 10, 2023

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


This bug is reproducible again
Creating a Split Bill from a group conversation freezes and an error appears in the console

Expected Result:

Successful Split Bill

Actual Result:

App crashes (Android)
App freezes (Web)

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.80.0

Reproducible in staging?: Yes

Reproducible in production?: N

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.462.1.mp4
Screen.Recording.20231010.135847.One.Ui.Home.mp4

An error appears in production

Screenshot 2023-10-10 134530

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

@izarutskaya izarutskaya reopened this Oct 10, 2023
@melvin-bot melvin-bot bot added the Overdue label Oct 18, 2023
@luacmartins luacmartins self-assigned this Oct 20, 2023
@melvin-bot melvin-bot bot removed the Overdue label Oct 20, 2023
@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Oct 20, 2023
@melvin-bot melvin-bot bot changed the title [HOLD #25714] Split bill - App crashes when splitting bill in group with both expensifail and gmail accounts [HOLD for payment 2023-10-30] [HOLD #25714] Split bill - App crashes when splitting bill in group with both expensifail and gmail accounts Oct 23, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 23, 2023

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 23, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 23, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.88-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

If no regressions arise, payment will be issued on 2023-10-30. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Oct 29, 2023
@puneetlath
Copy link
Contributor

I don't think anyone needs to be paid here, so closing out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Engineering
Projects
None yet
Development

No branches or pull requests

8 participants