Closed janbina closed 4 months ago
Yea telephoto is currently unaware of custom Coil fetchers for loading images. If it sees an Uri
, it expects the app to provide a content provider for reading its content.
I could potentially check for Uris that use schemes unsupported by ContentResolver
and read them using coil's fetchers instead. Wanna help me out? I'd start here:
Alternatively, can your custom fetcher return a diskCacheKey
? Reading images from the disk is significantly faster than reading them through input streams.
Closing due to inactivity, but feel free to reopen?
In our app, we are using uris with custom scheme to fetch a specific type of images. They are of this form:
We then have a
Fetcher
for coil that loads the image data from database, something likeThis works fine with coil, but telephoto tries to access the uri using
ContentResolver
and crashes:I'm not quite sure whether this should work or not, our solution is probably not great and maybe we should actually use
ContentProvider
for our uris instead ofFetcher
, but it worked so far 😀 For now we fixed that by using model class instead of plainUri
.