Ensure any callback action called from the CoilStreamImageLoader is run on the caller thread #5915
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…un on the caller thread
SDK Size Comparison 📏
|
VelikovPetar
approved these changes
Sep 8, 2025
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎯 Goal
The method
CoilStreamImageloader.loadAndResize()was run on the background thread to ensure any network call is not running on the UI thread. This Coil network call requires configuring a listener to perform actions after the picture is loaded, but it doesn't ensure the invocation was on the same thread, which could produce some errors if a UI component is updated there.With this change, we ensure the callback is run on the same thread the method was called.
Fix AND-718