HikingSeal

Just to bring an end to the thread. No I didn't replicate it. I didn't try to. With the site being down I just used the Send as Text feature, imported it into GSAK and finished my logging there. It was an individual log.
I guess it would be hard to build a safety net for this since it is a thankfully rare occurrence and what a user experiences as a site being down could be different in the background with the API.

I will say that we have a very open line of communication and that HQ is extremely helpful, kind and great people to work with. They really get a bad rap which frustrates me.

I originally thought that was the answer until I looked online and it was still there. Back to what I was originally going to type then.
I'm totally up for helping you promote Cachly. It's a product I believe in. Every log I send from Cachly says "Logged from Cachly" in the signature. That being said, could you add some space above the  "Log photo uploaded using Cachly" line? It's a really pain trying to get the cursor before it and I usually end up deleting your tag.
I also realize you're competing with the similar tag from the Official app that newbies aren't like to remove. Just looking for a compromise here for those of us who want to caption our photos and help you with promotion.

Yes, this feature was added to our beta probably over a month ago so has been tested by our beta users. It will for sure be in 3.0.

You're right. Totally misread that one. Sorry.

You're right. Totally misread that one. Sorry.

I had a feeling that was going to be the answer.  Just a thought.

I have a little data to add. It happened to me three separate times over Memorial Day weekend. Twice using the live map, once using an offline list. In all three situations I saved the log rather than sending. No matter what cache I tapped after hitting Done on the log screen the information for the cache I'd just logged came up. The problem was resolved by hitting refresh.in the live map or closing and reopening the app when offline. Again in all three instances, it did not happen for the next cache.
I couldn't replicate it at will either. Hopefully the observations will help.

For what it's worth, I too have experienced the problem. I'll try to keep an eye out when it happens again to see if I can replicate it. I superstitiously attributed it to my phone being nearly out of memory or having too many apps open. No real support for that thought as I didn't check my memory at the time.
 
P.S. Nic, if you don't recognize the handle, this is Chris Rock.  We've been chatting about my local event and the Maritime Mega.