-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-02] [HOLD for payment 2023-07-24] [$1000] Failed Room Termination: User Continues Chatting in Android App After Leaving Room on Web #21518
Comments
Triggered auto assignment to @johncschuster ( |
Bug0 Triage Checklist (Main S/O)
|
Working on reproducing this behavior this afternoon. |
Job added to Upwork: https://www.upwork.com/jobs/~012dc182ad93ca216b |
Current assignee @johncschuster is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
@rayane-djouah You need to manually set permissions in |
@allroundexperts why am i mentioned here 🤔 ? |
Ah, Sorry, I meant to mention @rayane-djouah. |
(...redacted) |
@johncschuster, @allroundexperts Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
ProposalPlease re-state the problem that we are trying to solve in this issue.Failed Room Termination: User Continues Chatting in Android App After Leaving Room on Web What is the root cause of that problem?The public room is re-opened on the second device (android) so the user will re-joined What changes do you think we should make in order to solve the problem?IMO, adding conditional logic to skip I'd propose adding an early return if the report is deleted. We can change this code: App/src/pages/home/ReportScreen.js Lines 162 to 170 in 7e908b1
To:
To determine if a report is removed because props reportID is possible to null when transitioning to a new report or not readily stored in Onyx. To prevent the page not found page shown before navigation, we can declare the new state:
and modify
Result - return onlyRecording.28.mp4Result - navigateToConcierge + returnnavigate.to.concierge.webmWhat alternative solutions did you explore? (Optional)N/A |
@wildan-m I noticed that with both our proposals, when |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@allroundexperts can you take a look at the above proposals when you get a moment? Do we need to keep looking? |
@nishancx, how can we refresh the page in the native app? |
I wasn't aware of that discussion, but I just caught up, thanks for the link. I agree that it's not a regression and that we should close out this issue once payment is issued. I also agree that we should create a new issue for the navigation requirement change. @wildan-m wanna report the issue and I can create it? |
@luacmartins sure, I'll post it to expensify-bugs, please wait |
@luacmartins posted here. |
@luacmartins good news! the requirement changes have been resolved by this PR. |
Cool, seems like we're all set then and just need to process payment for this issue |
👍 |
Bump @luacmartins, @johncschuster |
@johncschuster could you please help with payment? |
Bump @johncschuster, @luacmartins |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif ( |
📣 @wildan-m 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @avi-shek-jha 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
Ok, the job seems to not want to open back up. I'm going to create an issue just for payment for this. Standby. |
@wildan-m can you please go to the linked issue above and comment on it so I can assign it to you? That should get the job offer sent to you correctly. |
Hello, as a reporter, I only received an offer for 50 dollars. I am aware of the new policies. But, I reported this on June 17 and the issue was created on June 25 almost 2 months before the new policies took place. Can anyone please send me the offer link with corrected amount of 250 USD? |
Hi @avi-shek-jha, thanks for calling that out. I will correct that in Upwork. |
@avi-shek-jha, I've corrected that in Upwork. Can you please accept the offer? I'll take care of payment once you've done that. |
Thank you John. I appreciate it. I have accepted the offer. |
Ok everyone! I'm handling payments on this issue. I'm going to close this one out. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
When a user leaves a room on the web version, their participation in the room should be terminated across all platforms, including the Android app. They should not be able to send messages or interact within the room.
Actual Result:
After a user leaves a room on the web version, they can still send messages and participate in the chat room using the Android app. This behaviour contradicts the expected result and allows the user to continue engaging with the room despite their departure on the web.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.32-5
Reproducible in staging?: y
Reproducible in production?: y
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
first.web.mp4
second.android.mp4
Recording.871.mp4
Expensify/Expensify Issue URL:
Issue reported by: @avi-shek-jha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687048129225459
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: