馃悰 Bug Report
An iOS production build reported an unhandled SqfliteDatabaseException while displaying a cached network image. SQLite returned code 14 ("unable to open database file") for an UPDATE cacheObject ... WHERE _id = ?. Sentry recorded handled: no via PlatformDispatcher.onError. Image URL, SQL arguments, and user/device identifiers are omitted.
This resembles #494. A distinct concern is the cache-hit path in CacheStore._getCacheDataFromDatabase: it calls _updateCacheDataInDatabase(data!) without awaiting or handling the returned Future. If that write fails, the error can escape independently of the image-loading error path. The call is still present on main: https://github.com/Baseflow/flutter_cache_manager/blob/main/flutter_cache_manager/lib/src/cache_store.dart#L120-L127
The reason iOS could not access the SQLite file in this event is unknown; this report focuses on the unhandled asynchronous update.
Expected behavior
A cache metadata write failure should not produce an unhandled asynchronous exception. The cache manager should handle or surface it through an observed error path while keeping a valid cached file usable where possible.
Reproduction steps
The device event was intermittent in production; I do not have a deterministic device reproduction. An isolated test could create a valid cached file and metadata record, make the repository's updateOrInsert throw, then call CacheStore.getFile after a memory-cache miss. The cache-hit metadata update's Future is currently left unobserved.
Observed stack excerpt:
wrapDatabaseException (sqflite_platform_interface/src/platform_exception.dart:12)
SqfliteDatabaseMixinExt._txnRawUpdateOrDelete (sqflite_common/src/database_mixin.dart)
BasicLock.synchronized (synchronized/src/basic_lock.dart)
SqfliteDatabaseMixin.txnSynchronized (sqflite_common/src/database_mixin.dart)
Configuration
Version: flutter_cache_manager 3.4.2; cached_network_image 4.0.0; sqflite_darwin 2.4.3+1
Platform:
Flutter 3.47.2 / Dart 3.13.2.
馃悰 Bug Report
An iOS production build reported an unhandled
SqfliteDatabaseExceptionwhile displaying a cached network image. SQLite returned code 14 ("unable to open database file") for anUPDATE cacheObject ... WHERE _id = ?. Sentry recordedhandled: noviaPlatformDispatcher.onError. Image URL, SQL arguments, and user/device identifiers are omitted.This resembles #494. A distinct concern is the cache-hit path in
CacheStore._getCacheDataFromDatabase: it calls_updateCacheDataInDatabase(data!)without awaiting or handling the returned Future. If that write fails, the error can escape independently of the image-loading error path. The call is still present onmain: https://github.com/Baseflow/flutter_cache_manager/blob/main/flutter_cache_manager/lib/src/cache_store.dart#L120-L127The reason iOS could not access the SQLite file in this event is unknown; this report focuses on the unhandled asynchronous update.
Expected behavior
A cache metadata write failure should not produce an unhandled asynchronous exception. The cache manager should handle or surface it through an observed error path while keeping a valid cached file usable where possible.
Reproduction steps
The device event was intermittent in production; I do not have a deterministic device reproduction. An isolated test could create a valid cached file and metadata record, make the repository's
updateOrInsertthrow, then callCacheStore.getFileafter a memory-cache miss. The cache-hit metadata update's Future is currently left unobserved.Observed stack excerpt:
Configuration
Version: flutter_cache_manager 3.4.2; cached_network_image 4.0.0; sqflite_darwin 2.4.3+1
Platform:
Flutter 3.47.2 / Dart 3.13.2.