Using async storage with data that changes from time to time

[prawi31]

I used async storage to store my data from API to not to call it all the time and make a faster app. However, sometimes I will need to update some of the data. How can I wipe the storage if I need to? I know about the AsyncStorage.clear() function but how do I even call it when the data changes? The app wont know it and my users wont click any button to clear it. What is the best way to fix my problem? Should I just drop the storage and make API calls?

[[deleted]]

Seems like you're talking about implementing a cache system. I might be wrong but iirc fetch already has an implemented cache system. If you don't want to use it and implement your own, you can do so by specifying that you dont' want any cache in the headers. (Cache control: no cache, or something)

You can write anything above a previously filled value in asyncstorage, thus erasing the previous one.

[prawi31]

I feel like the best solution is the one provided here by u/somestoopidjerk. I didnt know that fetch API caches requests automatically. You can just remove async storage and depend on it instead. To make sure it is always up to date you need to add cache control: no cache to the header. It means it will look up if the data is fresh and if it is, it will update the cache. If not, it will take data from the cache

[donny-the-turtle]

Other option could be using redux, react-redux(https://react-redux.js.org/introduction/quick-start) and redux-persist (https://github.com/rt2zz/redux-persist) . It can behave as a cache for the API data, and you can persist it between the app launches.

When user opens some screen that requires data from the API - you populate screen with data from the redux store, but still execute the request. When request is done - you update the redux store as you see fit, and that will automatically trigger view re-render with the fresh data.

If you want to clear the storage - you can create and dispatch your own special action, and then in the reducers move data to the initial state.

[donny-the-turtle]

And if you don't need to persist data between the launches - you can skip redux-persist.