Trauerweide

39 minutes ago, Nic Hubbard said:

It is a server side bug. So a change that Geocaching HQ made to their API (not sure what) is now triggering the 500 error when full cache data and 100 caches are requested.

Oh, ok. Thank you for the explanation!

I've tested turning the "Full Cache Data" on with less than 100 Caches and that is working too. The maximum with "Full Cache Data" on seems to be 80 Caches.

Anyway, thanks for all your help! I'm really happy that I can now use Cachly again. ♥

40 minutes ago, Nic Hubbard said:

Do you have the "Full Cache Data" option turned on? If so, try turning that off and see if that helps.

Hi Nic, 

yes I had the "Full Cache Data" turned on and never had any problems with that before. So I'm really confused why this is making problems right now.

BUT...

I've try to turning it off and that solved the problem for me.

Thank you so much! ♥ ♥ ♥

40 minutes ago, Nic Hubbard said:

 

If it DID fix the issue, can you let me know what you have for the number of caches to load setting? Is it 100?

Yes it is 100.

I have send you an email with more informations and the debug data. I hope that helps you finding the problem. I would love to use Cachly again. It's way much better than the geocaching app! ♥

I have the same problem for several days but don't wanted to delete and reinstall Cachly yet. The geocaching app is working without problems. Is there anything that I can do to solve the problem without deleting cachly?