ChatView 2.2 Keyboard Hides in Mobile Browser

[kkruel8100]

Describe the bug
Updated to ChatView 2.2 for bug fix for gray screen in mobile browser.

To Reproduce
Publish web app
Go to Android tablet
Open Chrome
Use url link from published web app in Chrome browser
Go to text field and focus to type message

Expected behavior
Keyboard stays open so that the user can type the message

Actual behavior
Keyboard hides immediately

Note:
This is the "web" app and is accessible via the published url in a browser on mobile device. The mobile device is not using a mobile app. Need the web app to be accessible from the browser on the mobile device. Not able to recreate in "local" environment because this requires a published web app that is being accessed via the browser.
It works as expected in laptop/desktop browser local and published.

See issue #216 for video of behavior.

[vatsaltanna-simformsolutions]

@kkruel8100 I’ve tested the example on both iOS and Android browsers, and it works fine on both. Could you please share the reproducible code for further investigation?

RPReplay_Final1725444132.MP4

[kkruel8100]

Can you add the below code to FeatureActiveConfig to the example-test app that you have and then retest? The use case has these features turned off.

I think the example app assumes that all the features are enabled which is missing some of the use cases. Also opened a bug #254 that can be tested in local on a separate matter but referencing that to illustrate that the example app is assuming that all features are enabled which skews some of the testing.

enableReactionPopup: false,
enableDoubleTapToLike: false,
enableReplySnackBar: false,
enableSwipeToReply: false

[ElyasAsmad]

Need update on this. We are currently using this package for production and our users are reporting the same problem.

I have been trying to fix the problem myself by patching the package myself based on those:

• https://stackoverflow.com/a/55223950
• https://stackoverflow.com/a/71615482

Unfortunately, the problem is still there. I believe the problem is caused by unnecessary re-renders.

We will submit a PR once we found the solution

[ElyasAsmad]

Hey folks, I have conducted deep investigation to the library and found the root cause of this issue. PR #258 will attempt to fix the issue.

[vatsaltanna]

Thank you, @ElyasAsmad, for the PR. I’ll review it as soon as possible.

[ElyasAsmad]

Hello @vatsaltanna . Any update on this issue? It's been a month now since the PR is submitted. I hope you can merge it asap since there are other projects that utilizes your library.