Issue with @10play/tentap-editor on Physical Android Devices about 10tap-editor HOT 2 CLOSED

my package.json looks like this :

"dependencies": { "@10play/tentap-editor": "^0.4.58", "@expo/config-plugins": "^8.0.4", "@expo/metro-runtime": "^3.2.1", "@react-native-async-storage/async-storage": "^1.23.1", "@react-navigation/native": "^6.1.17", "@react-navigation/stack": "^6.3.29", "expo": "^51.0.9", "expo-doctor": "^1.6.1", "expo-status-bar": "^1.12.1", "react": "18.2.0", "react-dom": "18.2.0", "react-native": "^0.74.1", "react-native-gesture-handler": "^2.16.2", "react-native-safe-area-context": "4.10.1", "react-native-screens": "3.31.1", "react-native-vector-icons": "^10.0.3", "react-native-webview": "13.8.6" }

from 10tap-editor.

Hey, we tested running our examples on physical androids, without any issue.
Could you share the error you are seeing? If there is no error in metro, try open chrome devtools and inspect the rich text editor
https://github.com/react-native-webview/react-native-webview/blob/master/docs/Debugging.md#android--chrome (in our case the rich text component is the webview so add the webviewDebuggingEnabled prop to the RichText

from 10tap-editor.