Caching

Caching is supported on iOS platforms with a CocoaPods setup, and on android using SimpleCache.

Android

Android uses a LRU SimpleCache with a variable cache size that can be specified by bufferConfig - cacheSizeMB. This creates a folder named RNVCache in the app's cache folder. Do note RNV does not yet offer a native call to flush the cache, it can be flushed by clearing the app's cache.

In addition, this resolves RNV6's repeated source URI call problem when looping a video on Android.

iOS

Technology

The cache is backed by SPTPersistentCache (opens in a new tab) and DVAssetLoaderDelegate (opens in a new tab).

How Does It Work

The caching is based on the url of the asset. SPTPersistentCache is a LRU (Least Recently Used (opens in a new tab)) cache.

Restrictions

Currently, caching is only supported for URLs that end in a .mp4, .m4v, or .mov extension. In future versions, URLs that end in a query string (e.g. test.mp4?resolution=480p) will be support once dependencies allow access to the Content-Type header. At this time, HLS playlists (.m3u8) and videos that sideload text tracks are not supported and will bypass the cache.

You will also receive warnings in the Xcode logs by using the debug mode. So if you are not 100% sure if your video is cached, check your Xcode logs!

By default files expire after 30 days and the maximum cache size is 100mb.

In a future release the cache might have more configurable options.