-
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 #25467] [$500] Split Bill - Individual chats with each participant are not created in offline mode #26491
Comments
Triggered auto assignment to @CortneyOfstad ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~0104022d629ccfb887 |
Current assignee @CortneyOfstad is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
📣 @ayazalavi! 📣
|
Proposal Please re-state the problem we are trying to solve When splitting a bill while in offline mode, Besides group chat, individual chats with each participant should be created as well. What is the root cause of this problem? Assuming individual chats are created when online as mentioned in the problem statement. This can be due to 2 reasons-
In case this behaviour is also present in online mode, it narrows down to the first scenario and will be a straightforward fix. What changes do you think we should make in order to solve the problem? To begin, I would check the code for case#1 and test the creating individual chat functionality in offline mode. With these tests I would be sure about which scenario we face. For 1, Simply adding the logic for creating individual chats would suffice. If individual chats fail to be created in offline mode we would need to take a deeper look to figure out if it is possible to create them. If yes, I will add that functionality. Thanks! Upwork Profile Link: |
📣 @Rachit-pul! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Hey @ayazalavi and welcome! 👋 Please ask questions that are not related to the issue on Slack - it helps to keep things readable here. |
This comment was marked as outdated.
This comment was marked as outdated.
@ayazalavi Please see the "Expected result" section in the issue description.
@Rachit-pul Thanks for your proposal! As it stands the proposal needs more detail in both the RCA (where is the issue in the code and why is it an issue) and the solution (what part of the code would you change). |
This comment was marked as outdated.
This comment was marked as outdated.
@jjcoffee ^^^ TIA! |
@ayazalavi I'm unsure if your RCA is correct. How would you explain that the behaviour only occurs in offline mode? Your solution is also unworkable as that logic cannot be removed. Side-note: please copy links to the relevant code blocks rather than adding screenshots. GitHub will automatically render it as a code preview, see here for more info. Meanwhile, open to other proposals! |
@jjcoffee please look at my updated proposal. thanks |
@ayazalavi Your RCA doesn't explain why the behaviour only happens whilst offline. If you're interested in digging deeper, it might help to read into the offline-first patterns used in the app. @CortneyOfstad do you reckon we can increase the bounty here to get some more proposals? |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
No update yet |
No update yet |
No update yet |
I'm heading OoO until Oct. 25, so reassigning BZ to keep an eye on things while I'm gone 👍 |
Triggered auto assignment to @puneetlath ( |
Bug0 Triage Checklist (Main S/O)
|
This can be removed off hold since that PR has been merged. |
@puneetlath, @CortneyOfstad, @jjcoffee Eep! 4 days overdue now. Issues have feelings too... |
@jjcoffee should we remove the hold on this? Or is this now fixed? |
@puneetlath Unable to repro on latest staging v1.3.91-6 so I think we're good to close! |
Great! Thanks @jjcoffee 😄 |
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:
Expected Result:
Besides group chat also individual chats with each participant should be created
Actual Result:
Individual chats with each participant are not created
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.61-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
Bug6185035_Recording__830.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: