I've noticed an issue where TigerDine occasionally gets stuck loading when the cache was a hit and it's loading from there rather than fresh from TigerCenter. The app will stay on the loading screen and spin forever, and you need to restart the app. Once you do it'll load from cache immediately with no issues like normal.
Will need investigating because I haven't been able to figure out a definite cause yet, and there isn't any obvious output in the console that would indicate something is failing. Currently my best lead is that the read from UserDefaults is just running forever for some reason, since that data is force unwrapped and if it was returning something bad the app would probably be crashing instead. My only idea for why that might be is if maybe there's some sort of weird lockout if the widgets were reading from the cache to refresh themselves at the same time that TigerDine itself attempts to read from the cache? Not sure if this is a thing but I'm writing it down so I remember to look into it.
I can see the cache hit message print to the console when this occurs, so that confirms that it is specifically a failure in the cache load path and not the network load path.
I've noticed an issue where TigerDine occasionally gets stuck loading when the cache was a hit and it's loading from there rather than fresh from TigerCenter. The app will stay on the loading screen and spin forever, and you need to restart the app. Once you do it'll load from cache immediately with no issues like normal.
Will need investigating because I haven't been able to figure out a definite cause yet, and there isn't any obvious output in the console that would indicate something is failing. Currently my best lead is that the read from UserDefaults is just running forever for some reason, since that data is force unwrapped and if it was returning something bad the app would probably be crashing instead. My only idea for why that might be is if maybe there's some sort of weird lockout if the widgets were reading from the cache to refresh themselves at the same time that TigerDine itself attempts to read from the cache? Not sure if this is a thing but I'm writing it down so I remember to look into it.
I can see the
cache hitmessage print to the console when this occurs, so that confirms that it is specifically a failure in the cache load path and not the network load path.