Alex Grebenyuk
Alex Grebenyuk
Hi, are you still able to reproduce this crash? Is it OK to close the issue?
No, I don't think I've made any changes that could affect this part of the framework.
Please provide more details: the version you are using, the steps, and the expected and the actual result.
Please, go through the documentation on caching https://kean-docs.github.io/nuke/documentation/nuke/cache-layers. It sounds like it might be HTTP cache control issue.
I debugged the following scenario: ```swift let request = ImageRequest(url: URL(string: "https://i.imgur.com/k8gZbJ4.png"), userInfo: [..scaleKey: 3]) LazyImage(request: request) ``` The image displayed by the `LazyImage` appears to have the correct size...
I think the issue it due to coalescing and/or caching of the requests. The framework tries to minimize the amount of work and reuse the existing cached images and download...
My suggestions would be to either make sure you use the same scale every time OR disable coalescing using pipeline's configuration. I'm also going to mark it as a defect...
The coalescing issue were fixed in [Nuke 12.6](https://github.com/kean/Nuke/releases/tag/12.6.0).
I removed the sync cache lookup in 12.1.3 to fix https://github.com/kean/Nuke/issues/709. You can see what changed by looking at [this diff](https://github.com/kean/Nuke/compare/12.1.2...12.1.3). I over-corrected a bit, removing all optimizations because some...
Hey, @urbaneewe. If you'd like to kick this off, you are welcome to. The two main goals are: - Make sure there is only one `body` call when the image...