Nic Hubbard

Other apps have had this functionality previously - where all logs could be done offline, then all uploaded with a single action.
They do stop at their current point if they encounter an error at any stage (ie, a find log with no text) so you can then fix that error, and then start the send again from that point onwards.
I'm one that would make good use of this feature as I'm often caching in areas with no phone coverage, so using the app in an off-line mode.  Once you have many logs queued up, manually going in to each one of them and uploading individually is very time consuming (I did 50+ the other day like this on two occasions on a day with over 100 finds).
Especially useful when you need to go and add all the TBs in as you can't log them currently when there is no phone signal - although I know there's another feature request for that

This is something that we have on our feature list to add, but not sure when it will make it in.

Nic, I may have misunderstood DavSteph42 but he/she did say after you click one on the cache which loads the last log info.

For example I see the last five logs for this cache. Now that they are loaded it would be nice to see them above the gecache code in the list.

Of course for offline caches you should be able to show them all. 

A temporary workaround I'm using on this one is to include a couple of blank lines at the start of the template.  This then gives a large enough area to click in above the text to put the cursor to the beginning.

I've been using the updated beta version mentioned in the other post for a few weeks now.  I can confirm that it does a good job of allowing people in non-Seattle time zones to log caches at the "correct" date/time.

It shouldn't be too hard to automatically make the cursor start at the beginning of the text, so I will fix this.

Yes, this is a feature that we have been working on. However it isn't a quick and simple thing to add. Here is what has to happen with this feature:
Upload pending logs, one at a time to the server. If pending log has a trackable to log, log each trackable one at a time. If pending log has images to upload, upload images one at a time. So there are quite a few working pieces to this feature. That being said, we are still actively working on it.

This is an issue that was fixed in 2.0.2 which we will be submitting to Apple this week. Stay tuned. 

This is something that we are working on fixing. Basically we need to be updating the entire list for each GPS update we get. However, if it is a massive list this might have some performance ramifications, so we are working through this. 

Don't worry. I won't remove it.
Not a problem. Keep it coming!

Yes, it is just a simple quick search. A more advanced filtering feature will be added in 2.1.

I thought this might be the issue. I have so far been hesitant to fix this without more testing and here is why:
Say you have an offline list with 2000 caches. GPS returns a new location update every second or so. This would be the time to then update all the caches with the new location. However, you could imagine how this could start to turn into an issue if every second we tried to loop through 2000 caches and update their distance. Memory and CPU usage would be high.
To solve this issue I am going to update all caches at a longer interval, say 30 seconds. This should fix the bug while also not overwhelming iOS with trying to update a large amount of caches each second. 
Will work on fixing this bug. Thanks everyone for the testing and input.

Yes, this is a feature that we have been working on. However it isn't a quick and simple thing to add. Here is what has to happen with this feature:
Upload pending logs, one at a time to the server. If pending log has a trackable to log, log each trackable one at a time. If pending log has images to upload, upload images one at a time. So there are quite a few working pieces to this feature. That being said, we are still actively working on it.

Nic has a good answer for everything.

This is actually something we introduced way back in 1.0.4, but the overhead of converting logs with markup to attributed text was causing some performance issues. After that, we determined that few logs even use Markup, so we removed the feature and kept it on our feature list to fix the performance issues and add it again in a future version.

Huh.  That's weird.  I wonder why that is.  Although, now that you mention it, there was a recent event that was archived near me but it still shows up on the OFFICIAL app, which is definitely not supposed to happen.  So I wonder if that's an issue generated on Groundspeak's end with the way they archive certain caches.  (I noticed that the one archived event near me that kept showing up was archived by HQ, rather than by a local Admin or the Event creator... I wonder if that's somehow relevant).

Thanks Nic, that's awesome news!
Ketil

This is something that I have wanted to add for a while, so I made sure that I added it in for 2.0.2.

Hi,
Thanks for creating the best geocaching app out there.
I often save finds while in the field, and then compose and submit the logs when I get home.
What would really be a good feature for this workflow, is the ability to return to the cache listing from the pending log view.
Today, I have to search for the cache ID to find it, which is a bit cumbersome.
I typically do this to read through the description to get input on my log, and for mysteries I like to have a look at my cache notes to see when I solved it, etc.
Kind regards,
Ketil

I'm not sure how practical that would be, primarily because in most cases with letterbox hybrids you don't actually end up with corrected coordinates.  With mystery and multi caches, the final answer is usually just a set of coordinates that you plug in, but with letterboxes you're usually just following instructions, so unless you get to the final, take your own coordinate reading with your device at GZ, and then add in those coords, you're not likely to actually get corrected coordinates.

This is a great feature request, and something I have wanted to add for a while.

Running as a native iPad app — rather than 2× mode — has been in a few threads, but creating this separate feature request so it can be voted on.
Would be great if Cachly could take advantage of the large screen, including both rotations.
(And eventually split screen)

Saving offline didn't trigger the bug today.  The other actions I regularly do are to insert the Owner Name keyword, and after submitting going back to other logs before completely backing out of the cache.  I regularly switch between live caches and an offline list.  Still working on finding a consistent trigger 

As a previous geosphere user there were the option to update cache's by the following ways.
Basic cache data
Full cache data
Cache status
If an offline data was updated using basic cache data the corrected coordinates didn't disappear, only the cache information i.e. Logs and status was updated.
I not comparing cachly to geosphere this is just constructive feedback.

Thanks that seemed to fix it. I was using Apple map hybrid. I have switched to Google map hybrid and it works. Thanks for the reply. I'm really enjoying the app.