Fix Chatwoot Modal Crash Caused by Deprecated BackHandler #53
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carlmagumpara
approved these changes
Sep 9, 2025
|
+1 |
|
please merge this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #52
Clicking the
Xbutton on the Chatwoot modal triggers the deprecated error mentioned in the issue.React Native 0.77.0 deprecated
BackHandler.removeEventListener, which is still used by the version ofreact-native-modalbundled with Chatwoot. With Expo SDK 53 requiring React Native 0.79, this results in the reported error.The latest version of
react-native-modalresolves this issue. I have verified the fix by using npm overrides to force Chatwoot to use the updated version, and the modal now works as expected.