Skip to main content ↑ ↓
Topic: Logging caches with SLOW connectivity (Read 2310 times) previous topic - next topic

Logging caches with SLOW connectivity

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.

Re: Logging caches with SLOW connectivity

Reply #1 –
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.
 

Re: Logging caches with SLOW connectivity

Reply #2 –
A log is sent.