-
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
Android - LHN - Bottom of messages are cutoff #3538
Comments
Triggered auto assignment to @nickmurray47 ( |
Triggered auto assignment to @puneetlath ( |
Issue reproducible today during KI retests |
Going to be mostly OOO this week, so reapplying label so someone else can take it. |
Triggered auto assignment to @Jag96 ( |
@kavimuru so there is any other requirement on how to produce this issue? |
@aliabbasmalik8 I think that's because you have the #Focus enabled in preferences. Can you check? |
This issue not produced but we can fix it by increase the Here is what I see on android without any code changes. Thanks |
@isagoico I'm unable to reproduce this as well, on version 1.0.68-4. What version were you able to reproduce this on yesterday? |
Whoever reported this, can you check to see if you have any kind of font zooming enabled at the device level? Often times that can mess these things up. |
Yep, im unavle to reproduce either. I'll ask the tester who reported it. |
Sounds good, going to close for now, feel free to reopen if this is still an issue! |
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:
The text and emojis in messages are properly displayed
Actual Result:
The bottom of the messages are cut off
Action Performed:
Workaround:
Visual
Platform:
Where is this issue occurring?
Web
iOS
Android✔️
Desktop App
Mobile Web
Version Number: 1.0.67-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: