Markers flicker when scrolling on the map, React 18

[RamiShahazeh]

Markers displayed on the map is causing flickering on moving,

When we downgraded React to V17 is works fine, using rendering the App using ReactDOM but it will have some unexpected behavior in our components, so it's still not clear how can we remove this effect.

[wangela]

If you would like to upvote the priority of this issue, please comment below or react with :+1: so we can see what is popular when we triage.

@RamiShahazeh Thank you for opening this issue. 🙏 Please check out these other resources that might help you get to a resolution in the meantime:

• Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
• Open a support case - Get 1:1 support in Cloud Console.
• Discord - chat with other developers
• StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

[thepuzzlemaster]

@wangela (or others), can you elaborate a little bit on how actively this project is worked on? I'm considering switching over to this for my React google maps needs, but it's unclear to me how likely this issue (which I'm also experiencing in the current library I'm using) is to be addressed.

I don't see a lot of activity beyond version bumps any time too recently, nor much interaction in the issues/discussions boards.

Just trying to gauge overall likelihood of things like this being addressed.

Thanks.

[wangela]

@thepuzzlemaster We're committed to React support, more deeply than this wrapper. Stay tuned!

[itsmunim]

Hello @wangela

That's a great news, but is there a timeline we should be expecting?

[dungld96]

Any updates on this?

[AkramHarazem]

Any updates on this?

[karldanninger]

Bumpity bump, also facing this issue

[wangela]

Sorry I didn't remember to follow up here! For better Markers support in React, try https://github.com/visgl/react-google-maps (context at https://mapsplatform.google.com/resources/blog/introducing-react-components-for-the-maps-javascript-api/)

[usefulthink]

As for this issue, I'm not convinced that this has something to do with the wrapper component provided by this library. Can someone create an example (codesandbox or similar) that demonstrates this issue so I can look into it?