KCSearcher

I have observed the same behavior on my Windows10 laptop and my Android phone.

I just tried it from my laptop running chrome and my android. I am now getting the correct map results I expected. Problem seems to be resolved for me.

My issue is the same as described by ErewashPaddler. Any idea when this will be fixed?

Links I outlined in my original post are now working fine.

I am experiencing the same behavior. My Examples: Geodude2008 http://coord.info/PR2JZK8 https://www.geocaching.com/profile/?code=PR2JZK8 thedrainspies http://coord.info/PRGXNTK https://www.geocaching.com/profile/?code=PRGXNTK When they resolve, my profile is shown even though the https link is displayed in the URL line of my browser. Also, it indicates a warning the connection is "Not secure" .

It's working fine for me. I've had no issues with it since they fixed it back in June of 2019.

I sent an email a few minutes ago to 'Geocaching HQ Support' <contact@geocaching.com>. It had attachments the issue. Subject: Request {991696} [Google Earth Viewer issue] Body: Hi, It’s been a couple of weeks. Anything happening with this? Please review the attached files one again as they clearly documents the issue. The Google Earth Viewer is a very useful tool to do high level and sometime detail trip planning. This is significantly hindering that effort for my trip planning to New Mexico for the DeLorme and County Challenges. Once a fix is made, let me know and I’ll verify it’s behavior on the user end. Cache On!!! / Ken (KCSearcher)

Still not working as of 9/30/2016 5:38 AM PDT

Yes, I sent two this evening and did not receive my copy, even though it screen indicated an email was sent. I have now way of knowing is the intended recipient received the email. Is it stuck in some kind of software queue?

DATA POINT: As of Sun 8/21/2016 @ 7:17 AM, the most recent cache that I've noticed that did NOT have a notification email was GC6Q52W "What Three Words #3" (Unknown Cache) in California, United States created by lmt000. I noticed it live on Thu 8/18/2016 @ 4:09 AM Pacific Time. I have received emails on all since 8/18/2016 @ 4:09 AM.

Another thought. I should have mentioned this much earlier. How about backing out the changes made on July 26th until this can be tested and debugged in a development environment?

Issues noticed on Sunday, 7/31/2016 Pacific Time. List of 8 caches Published 8, only received notifications on 5. Most likely published at the same time, but maybe the Groundspeak logs can confirm that.

Looks like there still may be some intermittent issues. I received 5 notifications of the 8 caches published to 27-40 miles to the Northwest of Concord, CA this morning. Put a watch on them to see if the FTF hounds will get the ones that did not trigger a notification email.