I have an honest to god BUG in maps (regular, beta AND preview) and yet for some reason no matter what & where I try to contact the google support team, all I get are links to some FAQ’s that give me the runaround. Nothing there allows me to actually open a ticket with google, I’ve been searching now for well over an hour and am kinda desperate.
Additional to the advice given by @MortenCopenhagen , as well as letting Google know what you like or dislike about Maps and to suggest ways to improve the app, you can use this link to let Google know about bugs you’ve found.
Also, since you are new to Connect, you might like to have a look at Your guide to Connect. Another good idea is to introduce yourself in the monthly Community Introduce Yourself post.
I managed to open a support thread in the google help forum - apparently that’s only possible in the desktop version, on mobile the feature is simply unavailable. Let’s see if anyone is able to resolve the problem…
That’s great @viking84 . It’s also a good idea to come back here and update this post so that others who may have a similar issue in the future will know what steps to take.
By the way, wen responding to others here on Connect, it’s a good idea that you properly tag them so that they will get a notification of your message otherwise they may never know about or see your message or reply. To tag someone, first type @ then type the first few characters of their name until you see their name in the dropdown list. Finally, select the person’s name. You will see that I tagged you at the start of this message to you. Many think that this is done automatically when you reply to someone but it is not.
Thank you for reaching out. We are currently looking into it.
Just as a reminder, don’t forget when responding to others make sure to tag them (by writing @ before their names) in a post so they can receive notifications that you are communicating with them.
Unfortunately I don’t receive any replies on the google support forum whatsoever, so at this point I can’t really say its a working solution. None of the recent updates fixed the issue either.