You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To have a nice placeholder while the photo is being loaded from the server for both platforms, I am using the react-native-blurhash library. Below is a code sample of how I use it together.
onSuccess is called only once. When you reopen the app, the callback is no longer called, which may be because the photo is already cached, but even in this situation, I would like to understand that it is already loaded to remove this blur placeholder. I also use a FlashList for preview these images like a feed, which I think is also one of the reasons for this behavior.
P. S. Waiting for your response. Thanks for this great library
The text was updated successfully, but these errors were encountered:
StasKovalov
changed the title
onSuccess callback call only once
onSuccess callback calls only once
Jun 7, 2024
@StasKovalov thanks for the report. I'll take a look. Is this happening on both platforms?
FWIW, blurhash is supported on iOS and WIP on Android.
@gtokman, Yes, for both. I also found a bug for base64Placeholder, resizeMode does not work on it. The image that is in base64Placeholder, it just stretches randomly
Preamble
To have a nice placeholder while the photo is being loaded from the server for both platforms, I am using the react-native-blurhash library. Below is a code sample of how I use it together.
Reproduceable Code
Problem
onSuccess is called only once. When you reopen the app, the callback is no longer called, which may be because the photo is already cached, but even in this situation, I would like to understand that it is already loaded to remove this blur placeholder. I also use a FlashList for preview these images like a feed, which I think is also one of the reasons for this behavior.
P. S. Waiting for your response. Thanks for this great library
The text was updated successfully, but these errors were encountered: