-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Android - The archived room opened empty and did not disappear from the LHN page #11669
Comments
Triggered auto assignment to @PauloGasparSv ( |
@kbecciv what happens if you do a clean sign out and come back in, does it still occur? |
Also is that archived chat still pinned in this case? Or is it unpinned? |
If the chat is still pinned in this case, this is expected functionality and not a regression! |
@AndrewGable tested and couldn't reproduce if we assume its unpinned, and if its pinned thats fine! |
Will wait for your response before closing this out |
@johnmlee101 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Closing this out |
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 #11631
Action Performed:
Expected Result:
The archived room opens with conversation in past and should disappear from the LHN page when tap on it
Actual Result:
The archived room opened empty and did not disappear from the LHN page
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.12.2.
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug5766915_Record_2022-10-07-11-13-54_4f9154176b47c00da84e32064abf1c48__1_.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: