Jump to content

Ben H

Members
  • Posts

    299
  • Joined

  • Last visited

Posts posted by Ben H

  1. 7 hours ago, stanley90 said:

    In the last ~3 versions, when I try to delete a cache from a list, I get an error "Your geocache has not been removed". However, when I refresh the list, the cache is gone, so it actually deleted it.

    I tried to log out and back in and even uninstall the app, but it didn't fix the problem.

    Thanks for reporting your issue. Good news: we've already got a fix completed for that bug. It will be included in a release soon.

  2. On 1/1/2018 at 5:07 PM, Zargonians said:

    I was also having this same issue and came here to see if anyone else was experiencing the same thing.  Some of my solved puzzles showed up in the app at the solved coordinates whereas others for no apparent reason, would not show up at corrected coords (even though they do on geocaching.com).  I read through all of the info above and decided to delete my app and reinstall.  Even though it appears to be the same version as it was before I uninstalled/reinstalled, it solved the problem.  Also solved an issue I was having of taking a couple of minutes to load caches on the map.  Now, my solved puzzles are showing up at corrected coords on the map online as well as in the app and caches are loading on the map much faster as well!  I'm a happy camper!

    Thanks for describing how you addressed the problem with corrected coordinates. We certainly don't want players to have to delete/reinstall the app, so we're continuing to investigate the issue. To help us diagnose, could you answer a couple questions?

    • What app version, OS version, and device were you using when you had the problem? You can find all of that info at the bottom of the Geocaching app's Help & About menu.
    • Did you have lists saved for offline use when you had the problem with corrected coordinates? If so, approximately how many lists and how many caches saved offline?

    Thanks in advance for any additional info!

  3. On 12/20/2017 at 11:43 AM, Sherminator18 said:

    Is there anyway you could go into more detail about what the new assets for my hides and DNF's and new map controls actually are? I have the new update installed and I'm not seeing really any changes with the map.

     

    On 12/20/2017 at 0:56 PM, barefootjeff said:

    Yes please. Back when I went to school (admittedly a very long time ago) assets were things with monetary value but I doubt an accountant would place much value on my DNFs.

     

    On 12/20/2017 at 11:50 PM, pingurus said:

    Well, you can now turn the map for example and I guess the symbols in the right top corner are also changed.

    But I agree that it would be nice if changes were communicated in more detail.

     

    17 hours ago, CAVinoGal said:

    I can now filter the map based on type of cache, and size of container - I don't remember being able to filter  by those parameters before in the app.  You could filter by terrain and difficulty rating, but that was it.

    I don't know what is meant by "New assets for your hides and DNF's" either.  I'm not seeing anything different, unless it's options while you are actually creating a log entry; I haven't yet had the opportunity to do that with the app.

    Thanks for the feedback, everyone. The changes in this release were indeed subtle, which is why we chose to make it a 5.8.x release as opposed to 5.9. Sometimes we actually don't post release notes for these kinds of releases since they often lead to questions similar to these.

    For the curious, the things that look a bit different following this release include:

    • The map controls (centering/swivel mode and map type selection) have switched from circular to square and are now larger and easier to see/tap.
    • The map icons ("assets") for caches you've DNFed and caches you've hidden have been updated for better accessibility.
    • The format for player logs in caches and trackables has been updated to use consistent type and spacing.

    There was no change to filtering options in this release.

    I hope those additional details help!

  4. On 12/17/2017 at 11:22 AM, TeamDjango said:

    Funny. There are a lot of corrections, but on all our Apple devices (iPhone 5, iPhone 6, iPhone 7 and iPad 5) the size of an cache is reportet incorrect, but the graphic (the cirkle) is showing the right size. The 2 letters S and L are switched. The XS is displayed as XL and vice versa and the (S)mall is displayed as (L)arge ...

    The error was corrected once.

    Thanks for reporting your problem. To help us understand better, can you upload a few screen grabs of what you're seeing?

    I'm hoping that The A-Team's post above about Danish explains your problem, but I'd also like to make sure there's not a true bug.

  5. 3 hours ago, CacheSleuth said:

    When I was out geocaching this last weekend I noticed when I would log a find using the iOS app, it would show me my total number of finds after I submitted but that number was 20 less than my actual number of finds (1173 after logging in app vs 1193 actual total via website). Does anyone know why it would be different in the app after finding a cache? 

    The API fix for this issue has been released. Can you please relaunch the app and let us know if you're still seeing the problem? Thanks!

  6. 28 minutes ago, CacheSleuth said:

    When I was out geocaching this last weekend I noticed when I would log a find using the iOS app, it would show me my total number of finds after I submitted but that number was 20 less than my actual number of finds (1173 after logging in app vs 1193 actual total via website). Does anyone know why it would be different in the app after finding a cache? 

    Thanks for reporting. We're aware of the issue and working to get a fix out soon.

    • Upvote 1
  7. 9 minutes ago, grateful cacher said:

    I went to run a Found Caches PQ today (the one that can be run every 3 days). It says that I've found zero caches. When I look at the top of page, where it shows my user name, it shows zero finds. But my profiles shows everything normal, with the correct number of finds. What's happening??

     

    There was a hiccup in a release this morning that has already been rolled back. Is the find count back to normal for you now?

  8. 16 hours ago, Twinklekitkat said:

    If a user has over 9,999 finds it’s only displaying the first three digits and three dots and no capability to show the real total. 

    Other than that, great addition. 

    Edit:  just noticed it’s not all users over 9999. Some are displaying correctly. 

    Thanks for the feedback. We are aware that some find counts are not displaying as intended when you've set the system font to a larger size. To help better understand the issue, could you share a little info? Specifically:

    * What OS and device you're using. You can find all this info along with the app version at the very bottom of the Help & About section in the app (More-->Help & About).
    * What text size you're using. On iOS, this is under Settings-->Display & Brightness-->Text Size. It varies per device on Android, but should be something like Settings-->Display-->Text Size.

    Thanks!

  9. 10 hours ago, kyrasantae said:

    The update yesterday has broken the display of the app icon image on iPad. It just shows the default no-icon icon.

     

    3 hours ago, kunarion said:

     

    I got the same thing on my iPad Retina.  White icon with two black circles with an "X" through them.  It's still the familiar green logo on the iPhone.

    Thank you both for reporting the issue. We'll investigate.

  10. On 12/2/2017 at 10:30 AM, Ahuimanu Hui said:

    Well, I just checked the app again on both my iPhone 6s and iPad Air 2. They are both using version 5.7.4 of the geocaching app, and on both devices the date of the event is shown as Dec 01. Cachly of course has the correct date. By the way, although the date of the event is not shown in the text, the date is included with the accompanying pic (upper right corner).

    I will see if I can include screen captures to document this problem...

    3809AFEE-31CD-4387-AEDB-F770B12C26AA.png

    D3D459B2-89A1-407B-9882-57C7C6D208DB.png

    Thanks for providing this additional info. We fixed a similar bug on Android in the past few months, so we'll investigate to see if the same fix is needed here.

  11. 40 minutes ago, _scottbsays_ said:

    Does anyone know if there's any plans to update the iOS to allow it to take full advantage of the iPhone X's larger screen?

    Our 5.8 update will offer full support for the iPhone X. It is currently in review with Apple and should available within the next 1-2 weeks.

    • Upvote 1
  12. 2 hours ago, LSOEVE said:

    Why doesnt the order of field notes conform to the order I found the caches? I want to see the oldest field note on top of the page (as it was in the old design) and not need the go to the very bottom (which takes really long if you log hundreds of caches after holiday).

     

    2 hours ago, CAVinoGal said:

    Perhaps a toggle to sort  by oldest to newest, or vice versa, would be useful?

     

    Assuming you're referring to the new drafts page, there is already a sorting toggle available that lets you choose between showing the newest or oldest drafts first. Near the top of the page, click on "Newest" or "Oldest" to set your preference. See the attached screen grab.

    5a12741e5eafa_ScreenShot2017-11-19at10_14_34PM.thumb.png.ec8578c958b82491bb0035a5063a36c4.png

    • Upvote 2
  13. 4 minutes ago, Ranger1965 said:

    I do not understand why every time I open the app the usual intro panels have to be scrolled through. It is very annoying. 

    Thanks for the feedback.

    It looks like you haven't logged any finds yet. The introductory experience you're referring to will stop as soon as you've logged your first find.

  14. On 10/23/2017 at 1:28 AM, HHL said:

     

    10 minutes ago, barefootguru said:

    As a Mac user… see @HHL's post about hacking the URL — it's very cool.  Basically:

    1. Find the BM code for your list
    2. Edit that onto the search URL
    3. Your bookmark list will appear as search results
    4. Click the usual Map icon
    5. Profit

    If you're a bit techie you can install GSAK under something like VirtualBox.

    We do have plans to make that method of mapping a list on geocaching.com more obvious and easy. It's not an accident that the BM code for a list became a valid search query parameter. ;) 

    • Upvote 1
  15. On 10/17/2017 at 6:29 AM, m0bean said:

    I too have become more and more satisfied with the official geocaching app on iPhone.  Good job!  My one reservation is a little different.  I wish there was a summary of log types like on the webpage.  This is very useful information to me.  This helps me determine whether the last 3 logs being DNFs likely indicate a difficult cache or a missing cache?  I also wish it listed the find count with each username.  Were those last 3 DNFs from cachers with less than 10 finds each, or with many finds under their belt?  Makes a difference.  So, I still open the browser for this info.

    Ok, I guess that 2 remaining complaints.  But, still, very nice app now, overall:)

     

    Log Type Summary.PNG

    Thanks for chiming in. Although it will likely be a different experience than the digest you screen grabbed from the website, we're currently looking into ways to make the most recent log type more obvious/discoverable so that players have a better preview to decide whether they want/need to dig into the full list of logs. We're also working on adding the ability to view profiles for other players, which would give you the chance to determine a find count for them.

  16. 3 minutes ago, actualsize said:

    Thanks, as for the three dots, I do not see them in the iPhone app. Are you perhaps thinking of the Android app?

    If a cache is selected, but I have not pressed "start" to begin navigation, I see three dots in the upper right. But the choices are 1) Add selected to list; 2) Add all to list; 3) Share; 4) Open in Browser.

    If I am navigating after pressing start, the three dots disappear, replaced by an "i" in a circle, which only tells me the cache type (which, I might add, is of ZERO use to anyone but a first-time n00b. I knew what a "traditional" was my first 30 minutes into this hobby. This button is a waste of space, now that I think about it.)

    If I press or swipe "Log", the three usual choices (found, dnf, note) appear, but there are no dots in the upper right corner. I see no path to any other choices. The three "more" bars in the lower right seem to be there for general housekeeping functions. Are you certain you're not speaking of an Android app function that the iPhone app lacks? 

    Yep, definitely the iPhone app. :) Make sure you're tapping the (...) menu when you have a cache's full details open (i.e. the cache info takes up the whole screen). When you tap that menu with the full screen cache view, you should see the Report a problem option. I am assuming that you've updated your app version with the last 8 months. We added the Report a problem option in version 4.10 of the app which was released last February

  17. 2 hours ago, actualsize said:

    I can do everything I need to do with the new app. Today, after a series of steady improvements, I really love it. I've only ever cached with an iPhone, so I was PO'd when the old app was retired and this one replaced it. It was a rough start, but it's golden now. Better than the old one ever dreamed of being. (And better than its Android counterpart.)

    But...

    My one remaining complaint has to do with the filter section of the live search page. It has a pair of sliders - one for difficulty, one for terrain. That's great, but both of them have a serious flaw: you cannont swipe the sliders so their endpoints overlap at a single D or T. You can only ever do a range: If you want 3.5 you have to settle for 3 and 3.5 or 3.5 and 4. You can never set the filter to 3.5 by itself.

    So if I want to look for a specific D/T -- let's say 1/3.5 -- I have to create a desktop pocket query to do that. (I do love how PQs now automatically show up on the phone as a List, but I digress.) It does me no good to use the sliders in the field because I'll get 1/3, 1.5/3, 1/3.5 (the only one I care about) and 1.5/3.5. This is essentially useless, especially since the D/T info is not included on a list's Details page - I have to select a cache and open its page before I can see the D/T rating. This is a royal pain when I'm working on my Fizzy grid.

    What gives? The Android version of the app allows its endpoint sliders to overlap at a single D or T, and the old version of the iPhone app could do it, too.

    Please fix. I know you can! I keep waiting for it in one of your updates, but it never arrives!

     

    Thanks,

    actualsize

     

    PS: not vital, but I would like to have the Needs Maintenance log type added back to the app for in-the-field use. Notes do not cut it because a prolific CO probably doesn't read every log about every cache they own, and I don't ever do much at my desktop when I get home. As a result, it is hard to give the CO a heads-up about any broken or Muggled caches, or GZs ruined by landscaping or construction I run across. I can see why this may be a conscious decision to prevent overuse by n00bs, though. Maybe only let this show up if one is a Premium member? I suppose I could use the Message feature and do it that way, but then the reviewer doesn't see it, which makes it hard to move a deserving neglected cache into Needs Archived territory.

    Thanks for the constructive feedback.

    • We are aware with the bug you described regarding the iPhone D/T filter sliders and we're investigating fixes.
    • Needs Maintenance logs are available in the app already, just in a different spot than you may be used to. When you have a cache open in the app, tap the (...) menu at the yop right, then tap Report a Problem and you'll see the option the create a Needs Maintenance or Needs Archived log.

    I hope those answers help!

  18. 15 hours ago, twoofnine said:

    Ben, Hi. Alan here from the Isle of Man. On the topic of encouraging newbies to the game, can more be done to explain the logging of trackables. We have so many going missing now after newbie visits. 

     

    2 hours ago, tjmorgan1962 said:

    Yes please....I have trying to track down a Magic Ixalan trackable.....so I can help it move along...

    It seems they -the Ixalan trackables - are being kept / nixed or the finders are not logging them in so others can help the mission of the trackable along.

    CPT  Morgan.  Ixalan pirate fan.

     

    Thanks to both of you for the input. As we spend some time focused more on teaching new players in the app, helping them understand the right ways to interact with trackables is absolutely on our to-do list.

  19. 3 minutes ago, Team ToCCK said:

    Please put trail maps back into the app - like the open cycle map available in the original geocaching app. It is available on the website but would be much more helpful if it was available in the app which is what geocachers are using in the field. 

    Thanks for the feedback. Are you aware of the Trails map type that can be accessed via the map type selector near the top left of the map? Look for the icon that looks like stacked layers, tap there, then select Trails. As long as you're not zoomed out very far, that map type will let you see trails in the area you're viewing. Is that what you're looking for?

    • Upvote 1
  20. On 8/30/2017 at 6:27 AM, GeoMonkeyTiger! said:

    I've been working on a lot of puzzle caches recently and notice that the Android app seems very inconsistent in picking up the "Corrected" coordinates when entered on the website.  It seems very random-- some will pick up and some will not.  Some are caches I've solved a while ago and some are more recent ones.

    I hate to do a spoiler, but I thought an actual example might be useful.  

    I had solved GC4N902 a few weeks ago.  I entered the "corrected coordinates" on the website and they show up there (you can see in the screenshot below, they are italicized like they do when you correct).  But when I open the cache in the app, it only lists the posted coordinates (See second screenshot).  I also don't get the special icon you see for the "corrected" coordinates.

    As a counterpoint, I also solved GC3J5F8.  I did exactly the same action of using the "Corrected Coordinates" function.  It DOES show up in the app with the corrected coordinates and with the special icon on the live map.

    Screenshot_20170830-084955.thumb.png.b08dc0ca252cab2e9bcd4bebd0926f1d.png59a6bb357682b_MyCountry2.JPG.60007ac8d79b24d7c69572fb1a579fd0.JPG

     

    I have several caches that won't recognize the corrected coordinates in the Geocaching App.  Note that if I use a different app, they work just fine (the corrected coordinates are displayed).

    Is there something I'm doing wrong?  Is there something I can refresh?  Is there some way when I open a cache I can force it to retrieve the updated coordinates?  Or is this a bug that's being worked on?

    Thanks!

    (And on a positive note, I have to say that adding a special icon for corrected coordinates and moving it on the map is absolutely one of my favorite things you guys have done in a while!! It's awesome!! :D)

     

    On 9/4/2017 at 4:43 AM, pinguinino said:

    Hi All,

    I totally agree with You. This new feature showing a new icon and moving the cache to the final location in the live map is Awesome.

    But unfortunatelly, I've also noticed that not all caches are refreshed with the corrected coordenates. It is something random. And you cannot update the cache information !

    I asume that this is an application bug. Anyone with any information ralated to this issue?

    Thanks !

     

     

    On 9/22/2017 at 5:40 PM, mojostones said:

    I've been having the same problem for several weeks at least.  It seems like my more recent solves are having this problem. 

     

     

    On 9/23/2017 at 1:04 PM, MBQS said:

    Same problem.  I had a series of 100+ puzzles with corrected coordinates just entered this weekend.  The App does not show any of them as solved.  I am sure this was working in the past, or at least on certain caches, but can't get it working at all now.  Fortunately, plans changed and the 100+ cache run was not a go ... yet

    Thanks to all of you for reporting your problem. Could you please respond here with what version of the app you're using? You can find that at the very bottom of the Help and About section under the the ☰ menu at the top left of the main screen.

  21. 7 hours ago, grimaldi said:

    Observed behaviour:

    1. Select a mystery cache, press on "Start" for navigation, select "set solution coordinates" from the displayed menu
    2. Set solved coordinates, the mystery cache icon moves on the map and a different icon is displayed. Press Stop
    3. Select a different mystery cache, press on "Start" for navigation, select "set solution coordinates" from the displayed menu
    4. Set solved coordinates, the navigation line changes, but the cache icon does not move. 
    5. When pressing stop, the solution coordinates are not stored.
    6. Repeat 3
    7. Set solved coordinates, the mystery cache icon moves on the map and a different icon is displayed. Press Stop
    8. The solution coordinates are stored.

    Desired behaviour

    1-8 but without 4 and 5

    Thanks for reporting your problem. Special thanks for awesome repro steps and details about hardware and software!

    I walked through each of your steps above using identical hardware/software (app version 5.7, iOS 10.3.3, iPhone 6) and I'm unable to reproduce what you've described in steps 4 and 5. Each time I get the what you've described in step 2, even when I do several mystery caches in a row. I know it's a lot of ask, but any chance you could provide a video of the issue happening?

  22. 9 hours ago, coachstahly said:

    Only if the CHS algorithm doesn't take into account the D/T ratings.  Most cachers understand that the higher D rating means there's a chance they won't find it.  I would assume that the algorithm would also take that into account.  Perhaps each 1/2 star decreases the value of a DNF so as not to penalize a 1 star and 5 star D cache the same.  Again, this is conjecture but I'd be really surprised if they didn't take this into account.  IF they didn't, then it certainly would be a problem and would indeed discourage the hiding of difficult and clever caches.

    The CHS does take D/T ratings into account.

    • Upvote 3
×
×
  • Create New...