Despite my efforts, I'm encountering an issue with my quest app where it fails to reflect updated content from Addressables after the initial run. Upon investigation, it seems like the app is pulling assets from a local cache even after I've updated the content on my server.
To test this, I deleted the catalogs and bundles from the server and reran the app, confirming my suspicion – the assets were still loading, indicating the Addressable system was indeed relying on a local cache.
I am doing addressable groups-> build ->"Update a previous build".
Here's what I've already tried:
Ensuring 'Build remote catalog' is enabled in the settings.
Disabling 'Use Asset Bundle cache' from the group settings.
Confirming that the group settings allow changes post-release.
Despite these steps, the app persists in loading from the local cache rather than fetching the updated content. Any insights or suggestions on resolving this issue would be greatly appreciated.
P.S: with the same configurations and project everything works fine for android and iOS device, there seems some device specific issue with quest only.
