iOS - Chat - Text "is typing" is slightly cut off at the bottom

[kavimuru]

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:

1. Open app and login
2. As account B, type in the text box and immediately check the account A device
3. Verify there's a message indicated that user B is typing

Expected Result:

"Is typing" is not cut off

Actual Result:

"Is typing" cut off at the bottom

Workaround:

Visual

Platform:

Where is this issue occurring?

Web
iOS ✔️
Android
Desktop App
Mobile Web

Version Number:
1.0.77-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Expensify/Expensify Issue URL:

View all open jobs on Upwork

[MelvinBot]

Triggered auto assignment to @Beamanator (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[isagoico]

Adding the deploy blocker label since this is not reproducible in Build 1.0.76-2

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[roryabraham]

There's a good likelihood that this might be fixed by #3966 as well.

[isagoico]

Issue is still reproducible both on Android and iOS

[parasharrajat]

Ok. It seems that I may have caused this. I will look into it today.

[parasharrajat]

Can't reproduce it on android

[isagoico]

It's still repro on my side. Here's a closer looks on how it looks in my Android device

[parasharrajat]

Ok I will try different devices.

[Beamanator]

@roryabraham I'm still seeing this in main so I don't think your PR fixed it; @parasharrajat I reproduced the issue (barely) on Android here:

android	iOS

[Beamanator]

@parasharrajat which PR do you think could have broken this?

[parasharrajat]

@Beamanator I think this #3942

[Beamanator]

Hmm when I removed your changes from that PR I see this in android, so your changes may have almost fixed the issue haha. Do you see the same?

[parasharrajat]

So I just tested it on the smaller android device which is at version v1.0.77-2 and I didn't found this issue.

[roryabraham]

Going to try and fix this again

[roryabraham]

My latest attempt is here (it also fixes some style regressions). I'm not 100% sure if it will fix this issue because I've been unable to reproduce it so far. But again, I think there's a good chance that it might.

[Beamanator]

Looks great @roryabraham - tested, approved, merged 💯

[Beamanator]

I believe we can close this automatically b/c fix has been merged, no payouts are due.

[roryabraham]

@isagoico @kavimuru can we please retest this in 1.0.77-3 and verify if the issue is solved?