No. The security implications of us saving users passwords is not something we want. This is the reason why OAuth is used and connects with Groundspeak, so we don't have to save passwords.
In 3.0.3 when you are asked you re-authenticate you will be asked if you want to Logout or Cancel. You can cancel if you need to continue using Cachly. Previously it would log you out without any option.
GPX export has been greatly improved in our 3.0.3 beta. It removes the issue of an empty waypoint at each cache (this was the original coordinate waypoint), cleans up a log of the code and gives you export options.
Will look into moving to 1.0.1 and will do some testing in GSAK to see why it is showing the error about no/code ID.
Thanks for reporting!
I would't think this would affect anything unless there was a deep bug in iOS. That setting only changes a true/false value in the compass API for iOS.
I have had two users report this issue that their phones were not able to find their current location when in an area with No Service. Switching to another app worked correctly and found their location.
Has anyone else had this issue?
I tried to reproduce this issue on a hike up Mt. St. Helens with No Service but Cachly worked perfectly the whole time and there were no issues with GPS.
Just trying to track this bug down...
Actually, just testing this, deleting PQs form the downloaded section on the website, then refreshing in Cachly correctly removed them from the available list in Cachly.
Can you still reproduce the issue?