Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IOS ::: No suitable image URL loader found for assets-library://asset/asset #8741

Closed
blazerroad opened this issue Jun 9, 2020 · 3 comments
Closed
Assignees

Comments

@blazerroad
Copy link

Hi guys,
in IOS at this code :

<ImageBackground
                      style={styles.item}
                      source={{ uri: item.uri }} >
                      {selected && selectedItemCount.lenght > 0 &&
                          <View style={{ ...styles.countBadge, backgroundColor: badgeColor }}>
                              <Text style={styles.countBadgeText}>{selectedItemCount}</Text>
                          </View>
                      }
                  </ImageBackground>

item.uri is : assets-library://asset/asset.PNG?id=8602ACD9-04C2-4FA9-B8A1-F65E1C1299DD&ext=PNG

it work at andriod but IOS comes with this error :

[tid:com.facebook.react.ImageLoaderURLRequestQueue][RCTImageLoader.mm:510] No suitable image URL loader found for assets-library://asset/asset.PNG?id=8602ACD9-04C2-4FA9-B8A1-F65E1C1299DD&ext=PNG
2020-06-08 23:16:28.129

im using exp-camera , expo-media-library
that work fine on EXPO CLIENT app but after eject im getting this error
Screen Shot 1399-03-20 at 14 10 13

react version : "react-native": "~0.61.5",
xcode version : 11.4.1

Screen Shot 1399-03-20 at 14 10 13

@tsapeta
Copy link
Member

tsapeta commented Jun 10, 2020

Hi @blazerroad, which version of expo-media-library do you use? It's been already solved by #8304

@blazerroad
Copy link
Author

blazerroad commented Jun 10, 2020

I recently installed it so it should be latest version
"version": "8.1.0"
"_args": [
[
"expo-media-library@8.1.0",

@tsapeta
Copy link
Member

tsapeta commented Jun 11, 2020

Hmm ok, could you try version 8.2.1? It contains a fix for that 😉 It's been already published, but not promoted to latest tag on npm yet, so 8.1.0 is installed by default still.
As this issue is already solved in my opinion, I'm closing this thread but feel free to come back here if not 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants