React Native widget has major UI issues (keyboard overlap, input positioning) – need demo or clearer integration guide
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start by reproducing the widget in an Expo-based React Native app, focusing on keyboard opening, input positioning, and message visibility. Compare behavior with the suggested KeyboardAvoidingView and safe-area integration patterns. Done means the input remains visible and anchored, messages reflow without being hidden, and the recommended embedding setup is documented with a minimal demo.
Written by the indexing model from the issue text.
Description
Hi,
I’ve been trying to integrate the Chatwoot React Native widget into an Expo-based React Native app, but I’m running into multiple usability issues that make it very difficult to use in a real application.
Main issues
-
Keyboard overlap issues
- When the keyboard opens, it overlaps the message input field.
- The layout does not adjust properly, making it hard or impossible to see what the user is typing.
-
Input field positioning
- The message input (type widget) at the bottom is not anchored correctly.
- It either gets pushed out of view or overlaps with messages when the keyboard is active.
-
Message layout problems
- Messages do not resize or reposition correctly when the keyboard is open.
- In some cases, content becomes partially hidden.
Environment
- React Native (Expo)
- Latest version of the widget (from this repo)
What would help
At the moment, it’s unclear what the recommended integration approach is. It would be very helpful if you could provide:
-
A minimal working demo app (preferably Expo-based)
-
Clear guidance on:
- Handling keyboard behavior (
KeyboardAvoidingView, safe areas, etc.) - Recommended layout structure when embedding the widget
- Any required wrappers or configuration for proper rendering
- Handling keyboard behavior (
Right now, it’s difficult to determine whether the issues are due to incorrect integration or limitations in the widget itself.
Thanks in advance!
- Dominant language
- JavaScript
- Stars
- 81
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from chatwoot/chatwoot-react-native-widget
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
chatwoot/chatwoot-react-native-widget#56 · 1 comment · 1 reaction ·
-
BackHandler Error while closing ChatwootPossibly taken @shaiunterslak claimed this 125 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 50/100
chatwoot/chatwoot-react-native-widget#52 · 2 comments · 4 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
chatwoot/chatwoot-react-native-widget#41 · 2 comments ·
All issues in chatwoot/chatwoot-react-native-widget
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nearform/unbreakci#897 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
automation chore ci-cd consistency developer-experience difficulty: easy discoverability documentation enhancement github-actions good first issue help wanted hygiene priority: P3 seo shell yaml
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
swc-project/swc-next-issues#394 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#5790 ·
Maintainers usually reply within 1 day