Last post by Geooh GO -
Is it only when logging trackables during logging a geocache? More details and finding a pattern helps. Two separate transactions occur... log the geocache, then log the TB. Somewhere in the process maybe a network connection was lost or timed out leaving residual confusion. Sending me diagnostics in a situation like that may reveal something or sending me your user name so I can see if any bug reports occurred with your ID.
Last post by Geooh GO -
There is never a "completely offline" unless you go into airplane mode or disable the API. Descriptions have images in them and same with logs... those aren't automatically downloaded until viewed. If you have enabled viewing log upvotes, Groundspeak doesn't send them via a "full" retrieval, but only when you start viewing logs. When you start the app, Geooh will refresh your user information. Getting counts of the number of photos for a cache or trackable. Showing stats like elevation or county on a map... those don't come from Groundspeak.
Geooh is the most full featured geocaching app out there. Those features require data that isn't always automatically provided in an offline list.
I have a question about behaviour of Geooh Go app if it is completely offline. Why is it, that the app is still looking for servers although there is no signal. About half a minute or so it is looking to receive something before it switches to my offline list and map. Does anyone of you have an idea or maybe someone of the developer team can answer my question.
Last post by Vistalia -
I’m having a problem when logging caches in areas with slow connectivity. I usually log my finds together with a few default trackables on my list. Sometimes, after the screen shows that the log was submitted successfully, the app gets stuck while logging the trackables. The ‘working’ spinner disappears and it remains on the ‘Log Geocache’ page. I need to tap ‘Cancel’ to exit, and the cache I just logged still appears as unfound on Live Map (not changed to smiley). However, when I check the website, the log is already there. If I move on to log the next cache, the ‘working’ prompt reappears before I take any action in 'Log Geocache' page, as if the app is trying to resume the previous logging process. When I review the trackable logs, sometimes they were logged successfully after it appears, and sometimes they failed. This issue happens frequently, especially after I’ve logged several caches in a row. The only way to recover is to force-close the app and restart it, which is very frustrating.
