I am having problems with an app I wrote that fails on my actual watch but runs fine in the simulator. makeWebRequest is returning a -300 which is request timed out. The URL works fine in Safari from my phone and in the simulator so it definitely isn't timing out. Turns out the watch has cached a 301 redirect which is no longer in place. To work around this problem I had to add a parameter on the end of my URL so that it wouldn't pull from the cache and would actually contact the server.
So my URL went from something like this:
https://www.example.com/opendoor
To something like this:
www.example.com/opendoor
A few weeks ago I put a I mistakenly added a 301 (permanent) redirect on my webserver rather than a 302 (temporary) redirect. By design a 301 is a permanent redirect so technically the watch (Garmin Connect for iOS) is abiding by the standards and not contacting the original URL anymore. But surely there is a way to clear the cache in Garmin Connect so it will contact the original URL again.
Does anyone know of a way to clear the cache in Garmin Connect for iOS?