Hi everyone,
I’m experiencing issues with the MappedIn React Native SDK on Android due to the use of version 11 of react-native-webview, which seems to no longer be compatible with the latest versions of Android.
I’m using an Expo project and encountered the following issues:
With New Architecture: The build completes successfully, but the app crashes as soon as it tries to display the map WebView.
Without New Architecture: The build fails completely.
I also tried building the MappedIn example repo, but it also fails to build correctly.
Has anyone else experienced this issue or found a solution? One possible fix could be upgrading the react-native-webview version, but I haven’t found a working workaround so far.
Thanks for getting back to me! I did some more testing and noticed that your sample app uses a fairly outdated version of React Native. After further investigation, I managed to build my app correctly using SDK v5, but I had to make the following changes:
Disabled the New Architecture of React Native to avoid crashes and build failures.
Upgraded react-native-webview to version ^11 (installed 11.22.7) and not ‘11’ as mentioned in your official documentation. This fixed the WebView crash I was experiencing.
For now, everything seems to be working fine with these adjustments. However, I’d like to ask if there are any plans to:
Update support for more recent versions of react-native-webview (e.g., 13.x.x).
Make your SDK compatible with the New Architecture of React Native.
Thanks again for your help, and I appreciate any insights you can share on this!
Thanks for the update, glad to hear you have it working. We are planning to upgrade Mappedin SDK for React-Native to version 6, which should include all of the points you mention. We’re aiming to release it in the first half of this year.