Sometimes, you may see what we call "stale" content in the apps. This is almost always a result of performance optimizations, and can be caused by one of two things: local caching and server caching.
Local caching
In order to make the Audiorista apps fast and responsive, we store some of the data locally on the device for later use. This allows us to show ex. Browse layouts quickly when you navigate to them without having to load data from the server and show a spinner every time. When the user closes the app and re-opens it, we typically load the fresh data.
Troubleshooting the local cache
On Browse layouts, you can pull-to-refresh in order to reload the data from the server. Still seeing stale data? Then you might be running into server caching (see next section).
Server caching
Browse and Feed layouts contain a lot of data, so they're expensive to compute. For that reason, we store the current data in a cache so that it can be sent to many users without having to calculate it repeatedly. When we detect that a title or collection has been updated, we trigger an update of the cache. The next time the app loads the layout, it should receive the latest data.
Troubleshooting the server cache
If you're still seeing stale data after pulling-to-refresh on a Browse layout, the trigger that tells the cache to update might not have been fired. In order to fire it manually, go to the Audiorista dashboard and do one of the following:
- Go to the relevant Browse layout and make the stale item invisible and then visible again - this triggers an update of this particular item
- Go to the relevant Collection and click Save changes - this triggers an update of all layout items that reference this Collection
- Go to any Title and click Save changes - this triggers an update of all layout items in the project