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

[Califdan2]

This post needs a body

[bob frost]

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

[FeedbackCommunityMember]

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.

[FeedbackCommunityMember]

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

[FeedbackCommunityMember]

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.

[FeedbackCommunityMember]

Exactly the same problem, extremely annoying!

[FeedbackCommunityMember]

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

[rmoorlag]

Indeed, i'm having it on both Windows 10 creators update as MacOS 10.12.5. On both machines it appears with the latest LR update. 
https://youtu.be/wZ8rmDGOg-Y

[FeedbackCommunityMember]

Same problem for me. Makes using the maps useless

[DClark064]

Pete, you seem to be the only Adobe person taking any note of this issue.  This is a serious problem for many of us.  Can you provide some update on the status of an Adobe response.

[IamMac]

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

[mobycat100]

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

[IamMac]

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

[F. McLion]

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

[Smit K]

Hi,

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

Thanks,
Smit Keniya
Adobe Lightroom Team

[jackp22186528]

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

Very frustrating. 

[andren47571293]

I agree. Problem occured on iMac and MBP at the same time about 5 days ago. Both on the latest OS. Both LR 6.10.1. Problem started when on LR 6.8. Upgraded in the hope that that would cure it, but no.

[FeedbackCommunityMember]

I have the same problem..

Version von Lightroom: CC 2015.10.1 [ 1117303 ]
Lizenz: Creative Cloud
Betriebssystem: Windows 10
Version: 10.0

[IamMac]

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

[FeedbackCommunityMember]

+1
Lightroom 6.10.1
Windows 10 w. Creators Update

[FeedbackCommunityMember]

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

[Victoria Bampton LR Queen]

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!

[Franck Payen]

Thanks for acknowledging it. First I wondered if it was only my Lr version, but I guess it has to do with a Google Maps API update : I still had an old Lr5 version (that was way out of date) and I get the same flashing effect. On their announcements, you see a lot of activity on maps lately...

[FeedbackCommunityMember]

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.

[FeedbackCommunityMember]

Same problem here, MAC 10.11.6 LR 6.10.1

[IamMac]

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