I’d like to request a feature enhancement for the expo-image component: the ability to customize how cache keys are generated, especially useful when displaying local or static assets that may change over time.

Currently, expo-image uses the image URI as the default cache key (e.g. the URL string). This poses a challenge in scenarios where the underlying image content changes but the URI remains the same—common with local assets bundled via require() or static file paths. As a result, outdated cached images might still render even after an app update.