-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2024-11-18] [HOLD for payment 2024-11-14] [$250] Android - Chat - App crashes when trying to split expense #52099
Comments
Triggered auto assignment to @twisterdotcom ( |
Triggered auto assignment to @mountiny ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
This issue is repro only with Gmail account |
Job added to Upwork: https://www.upwork.com/jobs/~021854131328155845207 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann ( |
Looking for the offending pr for $50 |
Fixed screen-20241106-142053.mp4 |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.58-2 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 2024-11-14. 🎊 For reference, here are some details about the assignees on this issue:
|
@DylanDylann @twisterdotcom The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Straight revert PR that was CPed to staging, the authors been notified and there was no checklist to be paid on the revert PR so I think we can close this and the original author will retry the PR keeping this bug in mind |
Ah good point, thanks for raising. We discussed this at the same time in Slack where C+ helped to identify it too and seems like I created the revert PR #52112 before your comment (looking at the timestamps) so while I appreciate your help I think I would not issue a reward at this case since we managed to find the offending PR before your comment |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.59-3 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 2024-11-18. 🎊 For reference, here are some details about the assignees on this issue:
|
@DylanDylann @twisterdotcom The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.58-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Issue was found when executing this PR: #51849
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
User should be able to complete the split expense flow properly in any group chat.
Actual Result:
App crashes when opening a group chat and starting the split expense flow.
Workaround:
Unknown
Platforms:
Screenshots/Videos
0611.txt
Bug6656128_1730866334057.Split_Crash.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @twisterdotcomThe text was updated successfully, but these errors were encountered: