-
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
Android - Chat - Recent users displayed without user's name #2280
Comments
Triggered auto assignment to @koswalto ( |
Triggered auto assignment to @iwiznia ( |
Why does this issue have no labels? That's part of the triage. |
Triggered auto assignment to @SofiedeVreese ( |
Triggered auto assignment to @chiragsalian ( |
Posted to Upwork: https://www.upwork.com/jobs/~0129ce68cd6783d18b @chiragsalian you were auto-assigned, can you please review proposals if/when they come through and follow steps here? https://stackoverflow.com/c/expensify/questions/7676 . Thank you! |
@isagoico Clear app cache and then re-run the app. You should be able to reproduce. |
@isagoico, any update on retesting here? I'm just wondering if the issue is consistently reproducible once the cache is cleared. |
I was unable to reproduce this after clearing cache in build 1.0.20-0 |
Alright since its not reproducible im going to go ahead and close out the issue. If you feel otherwise feel free to reopen 🙂 |
Upwork posting removed. 👍 |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Expected Result:
Recent users displayed with user's name
Actual Result:
Recent users displayed without user's name
Action Performed:
Workaround:
Unknown
Platform:
Where is this issue occurring?
Web
iOS
Android ✔️
Desktop App
Mobile Web
Version Number: 1.0.15-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Issue is not consistently repro. We were able to reproduce 3 out of 5 times.
Video
Expensify/Expensify Issue URL:
The text was updated successfully, but these errors were encountered: