Remote Addressables - Check for Catalog Update Delayed in Builds

So I've been working on a project in which we've incorporated the Addressables system. We intended on utilizing the remote catalog feature so we can push remote updates for content in our app without having to actually push full app updates. While implementing this feature I've come across a variety of issues, all that lead me to believe that they stem from the "check for catalog updates" part of the package. It would appear that for some reason, in both Windows and iOS builds (but not in editor), it does not reliably recognize when a catalog file has been updated.

This doesn't occur the first time the app checks for a new catalog, but only on following checks. Sometimes it takes ~1 minute, sometimes it takes ~5 minutes, sometimes it takes ~10 minutes. It appears to be inconsistent in how long it takes for the app to recognize that the hosted catalog is an updated version. Due to this inconsistency, I can't be certain if it is a delay of some sort, or if there is some other bug in the code that checks for an updated catalog, but this is the behavior that I've experienced.

I've tested this with the auto-generated time stamp catalog names, the Player Version Override names, having "Disable Catalog Update On Startup" set to false, and also having it set to true utilizing the manual method of CheckForCatalogUpdates and UpdateCatalog. I've tried using CRC, not using CRC, using Asset Bundle Caching, not using Asset bundle Caching. I've tried so many different settings configurations and hosting solutions (Google Cloud, Private Server, Digital Ocean). I was pretty exhaustive in my testing, all the while scouring the forums for some sort of solution. Some of the issues I found I now think may have been as a result of this bug, including the CRC Mismatch issue mentioned here: https://forum.unity.com/threads/crc-mismatch.716303/.

I hope this is enough info to get an idea of where the issue might lie. Please let me know if you need any more. I would really love to solve this issue!

 

By the way I'm using package version 1.12.0