dan_hartford's profile

524 Messages

 • 

12.6K Points

Fri, Jun 16, 2017 8:03 PM

Lightroom: Map module keeps flashing "map offline" when it's not

Responses

1 Message

 • 

60 Points

4 y ago

Same problem here.
Windows 10 Pro x64
LR CC2015.9
Internet connection ADSL2+ Ethernet connected (not WiFi)

31 Messages

 • 

556 Points

4 y ago

Same here: W10 x64, CC 2015.10.1

2 Messages

 • 

72 Points

4 y ago

Same as everyone else apparently, Win 10 LR CC, all fully updated. LR CC 2015.10.1

12 Messages

 • 

422 Points

4 y ago

Alright guys and gals. Enough of the postings about the map offline error flashing. We have all learned that this has NOTHING To do what computer system one is on or what LR version is installed either . It pertains to all kinds of configurations. HOW ARE WE PROCEEDING FROM HERE ON? Can we push Adobe to get its bacon moved and give us an explanation of what to do about this or at least can we have a statement that they recognize the problem and working on it? This can NOT go uncommented on their behalf any longer. Any ideas? Thanks 

1 Message

 • 

62 Points

4 y ago

I also noticed also that when backing up catalog, in the optimizing step the white box flickers and turns black before closing. Both issues just started yesterday!
 

456 Messages

 • 

6.7K Points

4 y ago

I can also confirm this blackout and 'map offline' dialog is occurring everytime I move the map. Win10 and LRCC latest. Never happened before.


Bob Frost

1 Message

 • 

62 Points

4 y ago

Same problem here. It is annoying and I can't work with the map module.
I am running Mac OS Sierra 10.12.5 and Lightroom CC 10.6.1.
Seeing that many different OS version have this problem, it does not seem that it is a computer issue but more likely an LR or even a google map issue.

13 Messages

 • 

304 Points

4 y ago

Same problem here... Mac OS 10.12.5; Lightroom CC 2015.10.1

1 Message

 • 

82 Points

4 y ago

Here is video of the behavior (tip: it's annoying):
https://drive.google.com/file/d/0B4fNTUYL6CmdUnZlRDRTei1zblE/view?usp=sharing

Addendum: dragging a photo onto the map, it takes the software around 12-15 seconds to 'locate' the GPS and append the 'geotag' icon to the image in Lightroom; I have 200+ images to geotag in my current session, so that's ~50 minutes of waiting for the item to be geotagged (15 secs * 200 images = 3000 seconds). Unbelievable.

12 Messages

 • 

422 Points

Adobe where are you hiding. We need relief - SOON !!!!

31 Messages

 • 

556 Points

Probably enjoying the weekend ... like most of us too ;-)
Wait for Monday morning US time. I have filed a bug with Adobe.

12 Messages

 • 

422 Points

Thanks for filing my friend. Adobe has officially responded in the meantime as you might have read and is looking into it. I just hope they look hard, deep and fast and also catch the NEW bugs that were introduced into LR with CC 2015 6.10.1 and forced me to downgrade to 6.10.0

22 Messages

 • 

460 Points

Issue found in 6.9 as well (and poss also 6.8)  - reported on the LR Forum by me with no solution offered, other than restarting LR which does work (in 6.9 at least).  So it's not just a 6.10.1 issue alone, the underlying problem been there for some of us for a lot longer

Champion

 • 

6.5K Messages

 • 

109.5K Points

It's looking like it's possibly a server-side change at Google Steve, because it's affecting much older LR versions (e.g LR5) over the last few days too, and we'd have been sure to notice it for THAT long!

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

22 Messages

 • 

460 Points

Maybe part of the explanation why the number of users reporting the issue has escalated and that it's not just the latest iterations affected. However, it's been there for a while in the background.

12 Messages

 • 

422 Points

What are you talking about? The problem just started about six days ago. Everything was fine before !

22 Messages

 • 

460 Points

Norbert - I raised this on the Lightroom Forum last October.  It clears for me if I reload LR.  So it has some potential to be cache related as well as being a long standing bug that the recent changes to Google's servers has brought out.

129 Messages

 • 

2.8K Points

Google was changing their web certificate authority for Google Cloud Services starting June 12 so that may have something to do with this? Timing is about right.
https://gsuiteupdates.googleblog.com/2017/06/google-cloud-services-are-switching.html

-bh

9 Messages

 • 

162 Points

My tweet to Adobe 2 days ago has been left unanswered.  Not even an acknowledgement of said tweet.

Champion

 • 

6.5K Messages

 • 

109.5K Points

They've acknowledged it as a problem here Paul (although I can't answer for why the social team didn't respond).

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

9 Messages

 • 

162 Points

Ah... I missed that response.  (Their social team did respond just a little while ago saying this thread would have the most up-to-date info).

1 Message

 • 

62 Points

4 y ago

Exactly the same problem, extremely annoying!

1 Message

 • 

60 Points

4 y ago

Same problem here. Running Lightroom CC 2015.10.1
Windows 10 Home. 

1 Message

 • 

80 Points

4 y ago

Same problem for me. Makes using the maps useless

9 Messages

 • 

162 Points

4 y ago

I sent a tweet to Adobe's Lightroom account.  We'll see if there's any reply.

12 Messages

 • 

422 Points

Thanks Paul. Ironically the map is indeed offline at the moment the message is flashing.

Employee

 • 

295 Messages

 • 

7.8K Points

4 y ago

Hi,

We have logged the bug for this. We are looking into this.

Thanks,
Smit Keniya
Adobe Lightroom Team

37 Messages

 • 

820 Points

Thank you. 

6 Messages

 • 

234 Points

So, when will this bug be killed ? 5 days now you are looking inside ! ;-)

57 Messages

 • 

852 Points

Would be nice if this can be quickly resolved. Not only is it causing irritation and interrupts workflows, there also seems to be confusion at Adobe (a certain Mr Singh via Helpdesk chat suggested it's a proxy issue with my ISP provider, and when calling the German hotline, there was hesitant admission that the issue can be reproduced...). An rapid update that restores smooth operation is most appreciated!

2 Messages

 • 

96 Points

Basically the Map module is unusable. I understand this may be complicated issue, but still.. bunch of high-end coders and no solution for more than a week??? So disappointing!

2 Messages

 • 

110 Points

I'm rather dubious about the proxy explanation. I can see the logic - I work in an IT related field - but I thought it might be sensible to test this notion. As I had to go into work yesterday (Saturday) morning, I took the laptop in and connected it to the network.  The problem was still evident. It seems unlikely to me that my ISP and my work network, connected to the UK academic network made a similar change at roughly the same time. It looks to me like the most logical explanation is some change in the way that the Google maps API is working.

9 Messages

 • 

162 Points

@Iain Burke - agreed.  My work internet is connected directly (speed tests are always at a minimum 800Mbps up and down) to the same server farm that houses a LOT of high end stuff - think a certain gaming console from a foreign company.  The maps module doesn't work there nor at home with Cox Cable.

9 Messages

 • 

174 Points

There's good reason to be dubious about the proxy explanation because it's objectively false.  We didn't all simultaneously change our network settings just before this started.

12 Messages

 • 

422 Points

With more than nine million cloud subscribers and 1.5 billion profit it's time for Adobe to get this bug fixed after almost ten days now. To my knowledge there is no bug in my monthly subscription fee to Adobe Creative Cloud.

57 Messages

 • 

852 Points

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.

5 Messages

 • 

140 Points

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.

57 Messages

 • 

852 Points

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...

225 Messages

 • 

3.6K Points

2 weeks passed and you still didn't fix it?

54 Messages

 • 

920 Points

As of 3rd July 2017 I am still having the same map issue.

1 Message

 • 

66 Points

As of 5th July 2017 I am still having the same map issue.

9 Messages

 • 

174 Points

Hey Smit - Can we at least start getting monthly updates until this is fixed, or are you guys actively trying to antagonize your patrons?

9 Messages

 • 

174 Points

Hey Smit - Can we at least start getting monthly updates until this is fixed, or are you guys actively trying to antagonize your patrons?

13 Messages

 • 

232 Points

4 y ago

Same problem for me. LR CC 2015.10.1 running on macOS Sierra 10.12.5.

Very frustrating.