Ben H
-
Posts
299 -
Joined
-
Last visited
Posts posted by Ben H
-
-
New iPhone 7 using iOS 10.2.1.
I really like the new icons, but it's now taking me a frustrating number of taps to choose one.
UPDATE: About 15 minutes later. It went from 5-7 taps to choose/open an icon, to opening the first tap. Not sure what changed, but I'm happy. Thanks for the new release!
I'm glad that your issue seems to have resolved itself. Please let us know if you're experiencing it again. Frustration from non-responsive taps is certainly not the experience we're expecting people to have.
I've seen the same behaviour for newly published caches.
Pubished email comes in, click the hyperlink, app opens, invalid code message
This sounds like a temporary hiccup in our search indexing. As new caches are published, those caches need to be indexed in order to be searchable, which is of course required for them to be accessible in the app. During peak times there is a chance that the lag between publication and search availability could be slightly higher, but we're constantly working to minimize that gap.
How often has this occurred for you? How long after receiving the email have you encountered the problem? Any additional info might help us. Thanks!
-
Btw, it would also be nice to be able to open disabled caches in the app (when trying to do that now, I get a message saying that the GC code is invalid), the enable log type is a lot more useful then
Are you seeing that behavior after the update? If so, it's a bug we'll need to fix. Obviously we know that you need to be able to open disabled caches in order to submit an enable log for them.
-
We released an update today that should fix this issue. Please let us know if you continue to experience the bug after the update.
-
Will the app then display ones own disabled caches on the map?
Yes
Just curious, will this include the ability to search for disabled or archived caches (including ones you don't own)? Currently, if you search by the GC code of a disabled/archived cache, you get the message "Invalid code".
Yes, non-owners will be able to search by GC code for and view disabled caches. Disabled caches will also be viewable if they're already in a list/PQ/etc opened in the app. Like the classic app, disabled caches (other than owned disabled caches) will not show on the main geocache map in the app.
-
Ben, are there plans to add owner maintenance logs?
This is coming up in the next release.
Cheers!
Will the app then display ones own disabled caches on the map?
Yes
-
For me (using an API partner app, not Groundspeak's app), I like having the other caches displayed partially transparent.This is indeed a bug. Can you explain why it's important to you to see all caches when you're navigating to one?Part of it is awareness of context: I can see what other caches are in the area that I'll be visiting, so I can consider other caches I might want to search for after/instead of this one.
Part of it is a reminder that the app is still trying to navigate to a specific cache, and not showing me all the caches I'm interested in. If I see only one cache on the map, it isn't clear whether there are no other caches of interest in the area depicted, or whether the app is showing me only one cache because that's the cache it's navigating to. With the other caches displayed partially transparent, I know that they're there, but that the app is navigating to another cache.
Can you explain why it's important to you to see all caches when you're navigating to one?
This is a puzzling question. I can't speak for cachenscary, but the most important reason I like to see all the caches is that I sometimes pick the wrong next cache. If my GPSr didn't show all caches, I wouldn't see that I'm walking by another cache.
That's not the only reason. As cachenscary put it, I'm "always trying to stay aware of nearby caches in real time", both found and unfound caches.
Thanks for the responses with additional details.
I'm not sure exactly why the question is puzzling, but one of the worst mistakes I/we could make is not to understand why players want a certain feature. I could assume that you might want it for the same reasons I might want it, but those assumptions quite often prove incorrect. Hence the need to ask for additional detail.
-
I can't find any way to download PQ's in the new app. Is that feature no longer supported? If not, is there a way to cnvert a PQ to a list? How about .gpx to list? Gpx to list would be most awesome, as I often start with a PQ route then choose select caches to make a gpx file for download into my GPSr.
Hi there. Yes, you can download generated PQs in the new app during the same 7 day window of time you'd be able to download them to other API partners. You'll find them available for downloading offline in the Lists section of the app. To download one offline, tap the (...) menu to the right of the generated PQ and select Download Offline Data.
Working with the new app on my iPhone 6 the other day, I did something that resulted in red pins all over the map view indicating cache locations. They stayed in place even while navigating to a specific cache. I found that feature really helpful as i'm always trying to stay aware of nearby caches in real time. However, after about an hour the pins disappeared and I haven't been able to replicate that experience. Can you be of any help in recovering this capacity? Thanks.
This is indeed a bug. Can you explain why it's important to you to see all caches when you're navigating to one?
Bugs with Trackables when off line...
1) I created a list from the map
2) I downloaded the offline data whilst connected to wifi
3) Arrived at a cache where on the list it said there was a trackable (and there was).
4) tapped on the cache and opened up the cache page
5) Scrolled down to the trackables section where it said there wasn't any trackables in the cache
6) Come back home and connect to wifi
7) re-open the cache page and now it says there is a trackable
8) tap on the trackable icon and I am able to read all about it
9) turn off wifi
10) re-open the cache page and it still says there is a trackable
11) Tap on the trackable Icon again (wifi off)
12) opens trackable details but app message is presented "Oops something went wrong - try again later"
13) Click read goal - blank page opens
14) Cick description > Read More
15) App freezes then app crashes " Unfortunately, Geocaching has stopped.
Hi Ben, I'm using Android and v 5.02 of the app
Thanks! I'll pass your detailed info along to our QA team for investigation.
-
Bugs with Trackables when off line...
1) I created a list from the map
2) I downloaded the offline data whilst connected to wifi
3) Arrived at a cache where on the list it said there was a trackable (and there was).
4) tapped on the cache and opened up the cache page
5) Scrolled down to the trackables section where it said there wasn't any trackables in the cache
6) Come back home and connect to wifi
7) re-open the cache page and now it says there is a trackable
8) tap on the trackable icon and I am able to read all about it
9) turn off wifi
10) re-open the cache page and it still says there is a trackable
11) Tap on the trackable Icon again (wifi off)
12) opens trackable details but app message is presented "Oops something went wrong - try again later"
13) Click read goal - blank page opens
14) Cick description > Read More
15) App freezes then app crashes " Unfortunately, Geocaching has stopped.
Thanks for reporting the issue. Can you let us know which operating system version and app version you're using?
-
Thanks for the continued reports on this, everyone, and thanks for your patience. We have submitted an update to Apple with the fix for this bug and we're waiting for their approval. We hope it is approved soon so that we can release it next week.
-
Draft functionality is requiring a save of text before posting. This seems like an unneeded step. Perhaps this could be fixed?
I am using iPhone iOS 10.2.1
Geocaching Version 5
STEPS:
1) Open app
2) Click on a cache on the map
3) Click LOG GEOCACHE on the bottom of the screen in the green bar.
4) Choose an option like "FOUND IT".
5) Write some text in the log field. Remember this text.
6) Ensure that the "switch" in the lower right of screen is turned to DRAFT.
7) Click the SAVE option. A DRAFT SAVED banner appears.
8) Quit app.
9) Still on iPhone, reopen app.
10) Click the MORE option in lower right corner.
11) Click on DRAFTS
12) Click on the name of the cache with a saved draft.
13) Add additional text in the log field.
14) Turn DRAFT switch off.
15) Click POST.
16) Quit app, re-open app and look at the ACTIVITY of that cache to see your log.
EXPECTED RESULTS:
User would expect the text which was POSTED to be displayed in the log. ie: The text from step 13 should be displayed.
ACTUAL RESULTS:
The additional text added in step 13 was not posted. The log only displays the text from the last time the text was SAVED. (ie: the text from step 5 displays).
Thanks for the detailed report! That level of precision in explaining your problem is very helpful.
Fortunately, this is a bug we're already aware of and we already have a fix completed. We have submitted an update to Apple and are waiting for their approval. We hope it is approved soon so that we can release it next week.
-
Ah. This was on 4.0 of the app, thanks for clarifying. I missed the 5.0 update but will apply that tonight when I get back to wifi.
As for the TB synch issue, using app version 4.0 on a Samsung Galaxy S5 Mini running Android 6.0.1. TBs in question were TB3ERM1 (dropped off 4 FEB 17), TB6C6F1 (dropped off 17 FEB 17), TB2VGZC (dropped off 6 MAR 17), TB7F0PA (dropped off 6 MAR 17), and TB6C7AK (dropped off 6 MAR 17). Up until this afternoon, they were all still in my inventory until I opened each TB's description page in the app and they then synched up and disappeared from my inventory.
I don't think I used the app to pick up any of these TBs. The synch issue may have arisen because of subsequent logs. I am relatively sure I used the app to visit these TBs to a cache at least once; however, I did not use the app to drop them off, I used the website.
Thanks for the additional info. I'll pass it along for further investigation.
-
Ben, not sure if you're tracking, but the new app is having trouble synching trackables. I noticed it still listed bugs in my inventory whcih I'd dropped off weeks before. Only by viewing my inventory and clicking each of the errant TBs did it force the app to synch the TBs in question and remove them from my inventory. Per this thread, I am not alone.
While I'm on your radar, I'd also like the option of whether or not to list all of the TBs in my collection as being in my inventory on the app. I moved them to my collection so they wouldn't show up on a day to day basis, but all of the TBs in my collection show as being in my active inventory on the app.
Sounds like you may have multiple issues going on:
1) We made a fix in our 5.0 Android release that limited the TB inventory in the app to inventory only, no collection. Have you downloaded the latest version (now 5.0.2)? Please try that and let us know whether you continue to see trackables in your collection showing in your app inventory.
2) Thanks for the info on the syncing issue. We'll investigate. In the meantime, any additional info you can provide would be helpful for us to trace the problem (more detailed repro steps, your OS and app versions, links to the TB logs in question, etc). Thanks!
-
Caches on your ignore list are now filtered out from search results. If you want to open a cache you've ignored, you can still find it with a search by GC code.
-
I notice that there is still no way to filter out caches on the "ignore list" as there was on the classic app. Is this still in the plans to add? It would be greatly appreciated. Thanks
Caches on your ignore list are now filtered out from search results. If you want to open a cache you've ignored, you can still find it with a search by GC code.
Thanks for adding this functionality, and for quickly fixing a couple bugs with version 5.0.2. I normally use a GPSr, but entering field notes in the device can be a bit tedious. It's nice to now have the option of using the phone to create more detailed field notes and to be able to edit field notes that have been uploaded to the site, but not yet logged.
I really like that the beginning text of the field note is visible in the app without having to open each one.
I do have to reset my brain each time I open Drafts on the app, because it is ordered in reverse of what's on the website's field notes page. App shows most recent at top, while website shows most recent at bottom. Not sure that's such a bad thing, although for consistency it would be nice if both were the same.
Two requests:
(1) Having the time attached to the Draft log be correct. Presently, the time shown on the Field Notes page is 7 hours earlier than actual time. It was 8 hours before this past weekend. I understand this issue is connected to time zones across the entire app, whether a Draft log or a real-time log. Hopefully, this is something that's being worked on.
(2) A way to open the cache from the "Drafts" list. On the website, the cache name is clickable to open the cache page. Would be nice to see an "Open Cache Page" option in the Drafts "..." menu.
Thanks for the constructive feedback. We're currently working on our 5.1 release which will include a few small, non-drafts improvements and should be available next week. After that, our 5.2 release will focus on further improvements to drafts, including addressing both of your requests above. The time zone issues are indeed tricky, but we've got a new approach in the works.
-
For anyone still watching this thread, we added Drafts functionality in our latest release last week. More info in the release notes and on the blog:
http://forums.Groundspeak.com/GC/index.php?showtopic=343337
https://www.geocaching.com/blog/2017/03/3-reasons-to-write-great-logs/
-
Thanks for reporting the problem, all. We're working to fix the bug ASAP.
-
I'm using an iPhone 6 running 10.2.1 and had trouble after the update with the compass distance. The miles/feet number does not change as I get closer to the cache. The numbers under the cache title on the cache page to the right of the favorite points does change, giving accurate distance to destination. I haven't done much testing on other devices, but was wondering if this is a known bug.
Thanks for reporting your issue. A few others users reported similar problems, so we're investigating.
-
I notice that there is still no way to filter out caches on the "ignore list" as there was on the classic app. Is this still in the plans to add? It would be greatly appreciated. Thanks
We're working to implement this soon.
-
It seems that you can no longer actually log a cache whether in draft or normally. As soon as I got home and connected to wifi I was able to log caches and the draft option even showed up.
Thanks for reporting the problem. This is a bug which we'll fix ASAP.
Finally, It would be helpful if there was a global setting for drafts rather than having to select it every time.
The draft toggle's position is "sticky" across multiple logs. If you prefer to write drafts and switch to drafting mode on one log, you should continue to see the toggle in draft position on subsequent logs until you switch it back. Please let us know if that's not happening for you.
-
Thanks for these reports. We have confirmed the bug as reported. We'll get it fixed ASAP.
-
My app also shows the heart icon, it just doesn't work/do anything.
Hi there. Thanks for reporting your problem. I'd love to track down the issue if there is one. Can you give me a list of the steps you're going through to reproduce the problem and describe what happens when you go through those steps? Any screen grabs and/or info about your app version and OS version would also be very helpful.
Thanks!
Thanks for the offer.
Samsung Galaxy S5 Android 6.01 Geocaching 4.10 (not classic) I am a current premium member with 16 favorite points available
Find cache. Go to "log Geocache" Choose "Found it" Type Text for log Touch Heart Icon, it turns green Save log by touching check mark
The app saves the log, marks GC as found, but does not designate the GC as one of my favorites nor does my favorite point totals change. Verified log save and favorite failure on GCing .com upon return to home base computer. I have tried three different times to mark a GC as a favorite at time of find. Same non-result chronicled above. I did go back and favorite one of the failures from the Geocaching web page. However, I have left the last failure as is to prove the point. Last failure = GC12Y8N East of the pass.
So far, GC support has been no help. They asked me to reinstall app which I did. I reported back to them that it didn't work, no response from GC support.
If you need anything else, let me know. Thanks. SE&
Hello again! I just gathered a little more info and learned that we fixed a bug very similar to yours in our latest release (5.0.1). That release is currently trickling out to Android users; you may see it available to you later on today. Once you have the update, can you try again and report back whether your issue is resolved in the new version? Thanks!
-
My app also shows the heart icon, it just doesn't work/do anything.
Hi there. Thanks for reporting your problem. I'd love to track down the issue if there is one. Can you give me a list of the steps you're going through to reproduce the problem and describe what happens when you go through those steps? Any screen grabs and/or info about your app version and OS version would also be very helpful.
Thanks!
-
But I don't see anything in the web UI for that, so I gather these can only be created on the GPSr.
For now, you're right: you can not start a draft on geocaching.com. Today's release was primarily about adding drafts to the app. The website changes were more cosmetic to maintain consistency between app and web. We may revisit the tools related to drafts on geocaching.com as we continue to build out the feature in the app.
-
Hi there. This feature will be available in our next app release. You should see the update later this week.
Meters block compass
in Official Geocaching® apps
Posted
Thanks to both of you for confirming the fix. And sorry for the inconvenience while the bug was out.