Skip to content
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] AdvancedMarker custom icon not appearing #560

Open
usefulthink opened this issue Oct 2, 2024 Discussed in #558 · 2 comments
Open

[Bug] AdvancedMarker custom icon not appearing #560

usefulthink opened this issue Oct 2, 2024 Discussed in #558 · 2 comments

Comments

@usefulthink
Copy link
Collaborator

Discussed in #558

Originally posted by Remarketeer October 2, 2024
I'd like to ask for some help!

So a week ago I left my maps page alone to work on other stuff, but suddenly my markers disappeared. For some context, I have an array that I load information from and use .map to create markers for each entry. After some trial and error, I realized that it just wasn't accepting image inputs, e.g .

I've attempted to load the image on my other pages and that was fine. I've attempted to load Pin objects and that worked too, I've tried loading just a singular marker using an image source but it behaves the same way. Loading the image directly on the maps page also seems to work so the issue shouldn't be that. I'm quite stumped as to where it could have gone wrong.

Currently the data seems to have been loaded into the map as I've printed it to the console, but the marker just isn't appearing.

@mrMetalWood
Copy link
Collaborator

@Remarketeer I found an issue that would prevent a marker from showing when its width was set via CSS with a class on the AdvancedMarker element, but I'm not sure if that fits the issue you were describing. From the snippet you provided in the discussion it does not seem like it.

Could you provide a basic running example (on codesandbox or similar) where the issue exists?

@usefulthink
Copy link
Collaborator Author

@Remarketeer with the new version 1.4.0, this should be fixed. Can you re-check if you're still seeing the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants