-
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 04-17-2024][$500] Web - Split bill - Split bill shortcut directs to 404 page after splitting a bill with one account #39406
Comments
Triggered auto assignment to @lschurr ( |
@lschurr I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think that this bug might be related to #vip-split |
ProposalPlease re-state the problem that we are trying to solve in this issue.Pressing the split bill shortcut after splitting bill with one user leads to not found page. What is the root cause of that problem?When we open the split bill from the shortcut, the
And that's because Lines 4989 to 4995 in d7161ae
Lines 4802 to 4809 in d7161ae
That's why you can't see the split bill option from composer + menu, but you can still split with one user. What changes do you think we should make in order to solve the problem?Split bill with one user is totally valid, so I think we can start showing the split bill option for 1:1 DM too by removing the What alternative solutions did you explore? (Optional)If we don't want to show the split bill option in the composer + menu but still allow it from the shortcut, then we can:
|
Job added to Upwork: https://www.upwork.com/jobs/~01356e4f802ce02d01 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Split bill shortcut directs to 404 page after splitting a bill with one account What is the root cause of that problem?The
The issue here is within
as mentioned on the comment:
So What changes do you think we should make in order to solve the problem?We need to check if we are creatring the request from the Inside export default withOnyx({
// ...
+ quickAction: {
+ key: ONYXKEYS.NVP_QUICK_ACTION_GLOBAL_CREATE,
+ },
})(IOURequestStartPage); Add
POC video: 20240402_213028.mp4 |
Hi @jjcoffee - Could you take a look at the proposals on this one? |
Looks like we have an inconsistency here as @bernhardoj's proposal points out. We can create a split with a single user from the FAB, but it doesn't show as an option in a 1:1 chat (from the composer I'm not 100% whether there might be some reason for keeping the 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @NikkiWines, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Confirmed on Slack that |
Thanks for double checking @jjcoffee. Agreed that @bernhardoj's proposal looks good 👍 |
📣 @jjcoffee 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR is ready cc: @jjcoffee |
PR hit production last week (2024-04-10), so payment should be due tomorrow! |
Thanks for the bump @jjcoffee! |
Payment summary:
|
Paid! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v1.4.59-0
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Split bill shortcut should open
Actual Result:
Hmm... it's not here page opens
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6435487_1712058302059.35253.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: