Nic Hubbard

This was previously possible in Cachly, but with some recent iOS 13 changes it looks like I accidentally blocked that gesture. Sorry about that, I will fix that in an upcoming version.

Apple Maps (in developer apps) finally supports this in iOS 13, while the other map types have had this since Cachly 5.0.

In this case, go to the More > Highlights section and use the option to Manually sync highlights. Let me know if this fixes the issue.

Sadly that is the only way we have it setup to mail debug data. iOS doesn't allow a way to choose mail app.

There is currently an issue with some of the screens such as the More tab that are not getting translated. We are working with Apple to find the cause.

This is a dummy cache name that is used in development, but is normally replaced with the real cache name. Can you please replicate the error on your end, then right away use the Email Support option in the More take and make sure to include debug data. Then I will be able to see the API call that Cachly is making. Hopefully I will be able to replicate the issue.

We recently created a new Patreon page for those interested in supporting continued development of the app. So if you are interested in supporting Cachly's continued development make sure to head on over to our Patron page which includes multiple tiers with various benefits!

You can become a patron on the Cachly Patreon page: https://www.patreon.com/cachly There are various levels. I have tried to advertise it in various places but hard to get the word out to all users without spamming them, which I don't want to do. I need to check to see if Apple allows an app to open Patreon.

This is still being worked on. But for now, make sure on your iPhone that you have used the API (loaded some caches) and then try using your watch. This should allow the watch to get a new token which will fix the error.

Absolutely. I will be picking up my new Series 5 on Friday to build out this feature.

Glad that fixed it!

You say it used to work? Do you perhaps have a case with a magnet on it?

Strange. We haven't ever seen this before. If you test the Apple Maps app, are you able to active the mode that rotates the map? (Just wanting to see if somehow your compass isn't working)

After centering on your location, the next tap is "follow with heading" which should rotate your your map as you turn your phone. This isn't happening? Are you able to take a screen video for me so I can see exactly what is happening? https://support.apple.com/en-us/HT207935

Got it, you are meaning the current location button/follow mode button. When you tap it, what happens?

Nothing has changed in the last update regarding this. Do you mean you are not able to rotate the map with your fingers? Do you have the Setting for Prevent Map Rotation turned on?

Thanks for your detailed steps on this issue. I will work to get it fixed.

Yes they do but I do not have any record of this change. The different is the GPX is no longer including the "Z" in the datetime for timezone.

It looks like the date format in the PQ has slightly changed in the last while, so I put in a fix for this in our next version.

This should be fixed in our upcoming 5.2.6 version as I cannot replicate the issue anymore. Once we release that version let me know if you still see the issue.

It shouldn't, no. I have been running iOS 13 since it was available to developers in June and others have been running the public beta without issues. There are various bugs, but only one that I have seen affecting Cachly (choosing an image for a log from your photo library shows a blank image). Cachly will fully support iOS when it is released publicly this month.

Are you using iOS 13? If so, there are additional permissions that have to be added to allow Cachly to access photos. However iOS 13 will not be fully compatible until iOS 13 is publicly released and is no longer beta.

We haven't had this reported before. Can you replicate this issue? Have you made sure to allow Cachly to access your photo library?

Thanks, will keep an eye on this thread.

We have not had any reports about this. Cachly passes your local timezone to the API which then uses it to calculate your correct time. If this is the case, then I am not sure what has been causing it, we have not changed anything in Cachly and I wouldn't expect an API change on a Saturday. Can you replicate this issue?