Jump to content

Ben H

Members
  • Posts

    299
  • Joined

  • Last visited

Posts posted by Ben H

  1. I hadn't had a chance to circle back here yet. We temporarily rolled back some recent changes to security protocols that seem to have caused the issues with Garmin Express. We're investigating ways to re-deploy the updates without the associated problems.

  2. 14 hours ago, sayrahrah said:

    I've been successfully sending lists to my Garmin Oregon 450 using using Garmin Express. Now suddenly it won't work. I get a message saying" Request Error. There is a problem with the content being sent. Try sending the content again"  Has something changed? Is anyone else having this problem?

     

    4 hours ago, G & C Lost'N'Found said:

    I am having the same issue with my Garmin 64st. Spent 45 minutes on the phone with Garmin support but they couldn't find the problem on their side. Is it a Geocaching.com problem?

     

    3 hours ago, kunarion said:

    Same here.  I tried that, then sent the List to a Pocket Query and that worked.  I tried sending "Offline Data" from a List to the App, and that works, too.  And I sent a couple of "updated" from Garmin Express to my GPS, and it's fine. I'm sure the issue is temporary.  And I'm sure it's on Groundspeak's end.

     

    I hadn't noticed the issue, since I hardly ever load "Lists" on my Garmin Oregon.  Lists are not ready for prime-time.  They're ideal for the App, but there are several issues including this one, unanswered (in over a year?!), that let me know there are glitches built-in, and I don't want to risk losing data.  The Garmin is finicky enough, thank you very much. B)

     

    Anyway, if anyone's open to suggestions, you may make PQs out of lists, load them with the other PQs.  "Send To Garmin" has been broken for... how long?... and I didn't notice, because my lists are in the Pocket Queries.

     

     

    7 hours ago, Boswell5 said:

    Yes, from today I'm getting this problem sending to my Garmin Etrex 20 using Garmin Express. In the past I fixed a similar problem by adding https://www.geocaching.com/ to my Internet Explorer  trusted sites (you may want to try this anyway),  but I just checked mine and it's fine, so it looks like there is a new problem.

     

    We're sorry you're having trouble with the Send to Garmin feature. Thanks for reporting the issue.

     

    To help us diagnose what could be happening, could each/any of you share the following info about when you're encountering the problem?

    • What browser you're using, including version.
    • What operating system you're using, including version.
    • What version of Garmin Express you're using.
    • What Garmin device you're using.

    Thanks!

     

  3. Update - Yesterday, Google shared this information:

     

    "In collaboration with Huawei, Google engineers have identified the root cause of this issue as an unexpected change to the filesystem permissions.  The issue can impact any Android app on a Huawei device which renders a Google map. 

    Our engineers are preparing a new version of Google Play Services which should resolve the problem.  It will be targeted to devices running Android 7.0 Nougat, or higher.  We will post another update with the status of the rollout.

    Thanks for your patience."

  4. Update - Yesterday, Google shared this information:

     

    "In collaboration with Huawei, Google engineers have identified the root cause of this issue as an unexpected change to the filesystem permissions.  The issue can impact any Android app on a Huawei device which renders a Google map. 

    Our engineers are preparing a new version of Google Play Services which should resolve the problem.  It will be targeted to devices running Android 7.0 Nougat, or higher.  We will post another update with the status of the rollout.

    Thanks for your patience."

  5. Update - Yesterday, Google shared this information:

     

    "In collaboration with Huawei, Google engineers have identified the root cause of this issue as an unexpected change to the filesystem permissions.  The issue can impact any Android app on a Huawei device which renders a Google map. 

    Our engineers are preparing a new version of Google Play Services which should resolve the problem.  It will be targeted to devices running Android 7.0 Nougat, or higher.  We will post another update with the status of the rollout.

    Thanks for your patience."

  6. Update - Yesterday, Google shared this information:

     

    "In collaboration with Huawei, Google engineers have identified the root cause of this issue as an unexpected change to the filesystem permissions.  The issue can impact any Android app on a Huawei device which renders a Google map. 

    Our engineers are preparing a new version of Google Play Services which should resolve the problem.  It will be targeted to devices running Android 7.0 Nougat, or higher.  We will post another update with the status of the rollout.

    Thanks for your patience."

  7. Thanks for reporting your issues, everyone.


    The “Google Play Services are updating” error (displayed behind our app's error message that you've quoted above) is happening across the world to many different types of Huawei phones and tablets on Android 7.0, 8.0, and 8.1 (and very few other devices from other brands). Google is aware of the issue, and is treating it with top priority. They are aware that the problem occurs for many apps that use Google Maps (example: maps, games, ride-sharing, workout trackers, bus routes, etc.) Of course, this also affects Google Maps in our Android app.


    Currently, Android developers from around the world have found steps to temporarily fix the issue (disable, then enable, then update Google play services), but that temporary fix fails after the device reboots. We expect that after Google and Huawei fix the issue, the fix will be sent directly to Huawei devices. Then, after that fix is downloaded and installed, all of those apps that depend on Google Maps (and the associated Google Play Services file) will work once again.

     

    In the meantime, we're investigating whether there is any way that we can work around the issue on our end. So far, we've come up with potential ways to lessen crashes related to this Google+Huawei issue, but we don't yet have any way to fix the problem on our end. If we do find a way to fix it in our app, we'll release an update to the Android app ASAP.

    • Upvote 3
  8. Thanks for reporting your issue.


    The “Google Play Services are updating” error described is happening across the world to many different types of Huawei phones and tablets on Android 7.0, 8.0, and 8.1 (and very few other devices from other brands). Google is aware of the issue, and is treating it with top priority. They are aware that the problem occurs for many apps that use Google Maps (example: maps, games, ride-sharing, workout trackers, bus routes, etc.) Of course, this also affects Google Maps in our Android app.


    Currently, Android developers from around the world have found steps to temporarily fix the issue (disable, then enable, then update Google play services), but that temporary fix fails after the device reboots. We expect that after Google and Huawei fix the issue, the fix will be sent directly to Huawei devices. Then, after that fix is downloaded and installed, all of those apps that depend on Google Maps (and the associated Google Play Services file) will work once again.

     

    In the meantime, we're investigating whether there is any way that we can work around the issue on our end. So far, we've come up with potential ways to lessen crashes related to this Google+Huawei issue, but we don't yet have any way to fix the problem on our end. If we do find a way to fix it in our app, we'll release an update to the Android app ASAP.

  9. Thanks for reporting your issues, everyone.


    The “Google Play Services are updating” error (displayed behind our app's error message) is happening across the world to many different types of Huawei phones and tablets on Android 7.0, 8.0, and 8.1 (and very few other devices from other brands). Google is aware of the issue, and is treating it with top priority. They are aware that the problem occurs for many apps that use Google Maps (example: maps, games, ride-sharing, workout trackers, bus routes, etc.) Of course, this also affects Google Maps in our Android app.


    Currently, Android developers from around the world have found steps to temporarily fix the issue (disable, then enable, then update Google play services), but that temporary fix fails after the device reboots. We expect that after Google and Huawei fix the issue, the fix will be sent directly to Huawei devices. Then, after that fix is downloaded and installed, all of those apps that depend on Google Maps (and the associated Google Play Services file) will work once again.

     

    In the meantime, we're investigating whether there is any way that we can work around the issue on our end. So far, we've come up with potential ways to lessen crashes related to this Google+Huawei issue, but we don't yet have any way to fix the problem on our end. If we do find a way to fix it in our app, we'll release an update to the Android app ASAP.

  10. Thanks for reporting your issues, everyone.


    The “Google Play Services are updating” error described and shown in the screen grab above is happening across the world to many different types of Huawei phones and tablets on Android 7.0, 8.0, and 8.1 (and very few other devices from other brands). Google is aware of the issue, and is treating it with top priority. They are aware that the problem occurs for many apps that use Google Maps (example: maps, games, ride-sharing, workout trackers, bus routes, etc.) Of course, this also affects Google Maps in our Android app.


    Currently, Android developers from around the world have found steps to temporarily fix the issue (disable, then enable, then update Google play services), but that temporary fix fails after the device reboots. We expect that after Google and Huawei fix the issue, the fix will be sent directly to Huawei devices. Then, after that fix is downloaded and installed, all of those apps that depend on Google Maps (and the associated Google Play Services file) will work once again.

     

    In the meantime, we're investigating whether there is any way that we can work around the issue on our end. So far, we've come up with potential ways to lessen crashes related to this Google+Huawei issue, but we don't yet have any way to fix the problem on our end. If we do find a way to fix it in our app, we'll release an update to the Android app ASAP.

    • Upvote 1
  11. On 3/24/2018 at 5:51 AM, Xavier57 said:

    Hi, same thing here. On iphone 6 and last IOS version, my compass is often off, and I can only progress loooking the distance indicator. Same behaviour in the woods, in the streets or in the snowy mountain !

    I hope that it will be fixed soon !

     

    4 hours ago, seven_neves said:

    Same problem here.  I wouldn't say that my compass 'points in the wrong direction', mine is more like it's just frozen in a random position.

    Like other users the distance still ticks down on the app, so at present i'm playing a little game of Hot/Cold to make my way to the cache if I can't line it up geographically.

     

    It started after I recently did a bulk app update and GC app was in there too.  I've made no changes to the OS since the problems started, so the app update is the only thing I can pinpoint for my device as it was working perfectly prior.

     

    I find if I soft reset the phone I might get one cache out of it before the screen locks and the compass freezes again after unlocking the phone.

     

    Will update my OS shortly and see if that helps.

     

    Have either of you tried checking the "Compass Calibration" setting I discussed in my January 9 post above? Settings --> Privacy --> Location Services --> System Services --> Compass Calibration

    • Upvote 1
  12. 4 hours ago, Noobuddy said:

    Hello,

     

    if I create a bookmark list containing an umlaut (ö) it is replaced with Unicode (ö). Trying to rename it on the website doesn’t help either.

     

    I would greatly appreciate it if you can fix it. Thank you very much in advance :)

     

    Best regards,

     

    Noobuddy

    DB0A2B94-EF68-4FA2-B22C-4B8A9E2C53B8.jpeg

    Thanks for reporting this issue. We are aware of the problem and working to get a fix out. 

    • Upvote 1
×
×
  • Create New...