Unfortunately there is no workaround at the moment, since it's affecting all versions. Either Google will have to make a change on their servers, or Adobe will have to update Lightroom to work with Google's changes. The engineers will be figuring out the quickest solution right now, but I would anticipate it taking a few weeks, to be completely honest with you.
Customer support *should* be aware of it already, but whether the individual members of staff remember what they've been told is always a bit of a lottery. 😉
Victoria, your comments are most appreciated, thanks. I would further suggest that (a) knowledge of the bug is circulated among the Helpdesk/support team at the company (which would avoid lengthy and embarrassing discussions) and (b) that Adobe proposes a workaround for the time being. As a customer to some degree I don't really want to depend on whether or not the two companies can get along well or not... just my thoughts.
aurin r, this is the best place to get updates on problems. A user blog would just end up duplicating everything here. You'll note at the top of the page it says "acknowledged", which means they've been able to reproduce the problem and are working on a solution.
Since it's affected even old versions of Lightroom without Adobe changing anything, this would suggest it's a change on Google's servers, so they'll be working with Google to find a solution (but you know what happens when 2 big companies try to work together...!)
Same here in Denmark, obviously a adobe cloud issue since all kinds of windows and mac computers from around the world is affected. Would be so much better if Adobe had a user blog with updates on problems, descriping clearly a "Don't panic, this is all our fault on our server, we try to fix it though have no idea when it will be working again, since our lightroom team is currently on vacation..."
Regrettably, big IT companies are among the most arrogant organisations. This includes cable providers. Intransparent, slow moving/inflexible and customer service hopelessly incompetent (because the engineers are sealed away in a silo) - it's not a bug, it's a feature...
Exactly ... Adobe is one of the largest software house on the planet, yet its problem management and customer communication simply sux. Would it be my firm, all these people would be fired immediatly.
Even if a change of the Google maps API is causing the trouble, it would still seem incumbent on Adobe (a) to detect the issue and inform its users (it's 1 out 7 modules, =15%, that stopped working) and (b) to provide a timeline for its resolution.