-
-
Notifications
You must be signed in to change notification settings - Fork 860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Android - (NOBRIDGE) ERROR Error: Unsupported top level event type "topRct.mapbox.map.change" dispatched #3583
Comments
Just to note this is a dupe of #3493 |
Has there been any actual update on this issue as the linked dupe of #3493 is closed without a resolution to the problem? |
I am also having the same issue with react-native: 0.75.2 and @rnmapbox/maps: 10.1.30. Any solutions yet? |
Could we please get an update here? This is a blocker for me to use the new architecture in my app |
Related bug in other libraries:
Seems like maybe some handler isn't getting registered? I'll keep looking into this a little bit more. |
Can you try https://github.com/rnmapbox/maps/releases/tag/v10.1.32-rc.0 it contains #3656, which might fix the issue. |
@mfazekas this RC version has stopped the errors in the console and stopped the crash when opening the map on device Edit: nvm it is working, thanks for all your help |
I'm seeing this error on Android with the release candidate above "@rnmapbox/maps": "10.1.32-rc.0",
"react-native": "0.74.5",
"expo": "51.0.38" |
Mapbox Implementation
Mapbox
Mapbox Version
default
React Native Version
0.74.5
Platform
Android
@rnmapbox/maps
version10.1.28
Standalone component to reproduce
Observed behavior and steps to reproduce
When the map loads the following error occurs:
(NOBRIDGE) ERROR Error: Unsupported top level event type "topRct.mapbox.map.change" dispatched
To reproduce:
1 - enable new architecture in gradle.properties of the android project.
2 - Build project
3 - Start project
Expected behavior
Map to load without errors
Notes / preliminary analysis
No response
Additional links and references
No response
The text was updated successfully, but these errors were encountered: