[Android] Default markers are generated and persist where clusters used to be

[kimthompson]

This issue only happens on Android, and might be a side effect of something much deeper in React Native or React Native Maps. That being said, when we attempt to use the clustering library on any Android device, we see the following behavior:

Markerspawn.mp4

A minimal reproduction can be found here, provided you provide your own Android map key in the android/app/src/debug/AndroidManifest.xml file. Simply pull it down and run npm install, npm start, and in another terminal, npm run android.

Here's a section of our package.json, for quick reference:

    "react": "19.1.0",
    "react-native": "0.80.2"
    ...
    "react-native-map-clustering": "4.0.0",
    "react-native-maps": "1.25.3",

This reproduction uses React Native 0.80.2, but the same behavior exists in our actual app, which is using 0.78.2. I spun up other minimal examples using 0.78.3 and 0.79.6 as well and saw this same behavior.

[ondrejvrabel]

Having the same issue unfortunately.

[noahvanfleet]

Also having the same issue

[ondrejvrabel]

Probably related to react-native-maps/react-native-maps#5669

[AlexDelasalle]

Experiencing the same issue, It seems that it's related to clustering as I can't replicate if I stop using clustering
Do we know if there is a fix for this yet?

[kundanthe]

Any luck on this...I am seeing same issue

[markwilcox]

We have the same behaviour with custom markers and react-native-clusterer. We've temporarily managed to work around it by setting the marker image to a small transparent square image, as well as rendering the customer marker (using react-native-svg and text).

[ChromeQ]

After literally days of trial and error, build woes, headaches, heartbreaks, false hopes, hassle and eventual acceptance, I can finally give my full and honest review and solution over here:
react-native-maps/react-native-maps#5739 (comment)