[🔥] No suitable URL request handler found for ph://11B72114-7060-453B-A838-554A0B952C02/L0/001

[zfogg]

Issue

When using the <MessageInput /> component and trying to select images from the user's image gallery, the following error is produced:

No suitable URL request handler found for ph://11B72114-7060-453B-A838-554A0B952C02/L0/001

RCTHTTPRequestHandlerCls
    RCTNetworking.mm:712
RCTImageEditingManagerCls
RCTImageEditingManagerCls
7DE7EC03-CFB7-349D-9B9E-8782B38F231D
7DE7EC03-CFB7-349D-9B9E-8782B38F231D
7DE7EC03-CFB7-349D-9B9E-8782B38F231D
7DE7EC03-CFB7-349D-9B9E-8782B38F231D
7DE7EC03-CFB7-349D-9B9E-8782B38F231D
7DE7EC03-CFB7-349D-9B9E-8782B38F231D
_pthread_wqthread
start_wqthread

Steps to reproduce

Steps to reproduce the behavior:

1. Use the default installation instructions to setup expo and stream
2. Render a <MessageInput />
3. Open your media gallery on iOS with ph:// files in your gallery
4. See error pop-up. You'll also notice that ph:// files in the gallery are blank spaces instead of image previews.

Expected behavior

You should just be able to browse your media with no errors.

Project Related Information

Customization

Click To Expand

Offline support

• [ ] I have enabled offline support.
• [ ] The feature I'm having does not occur when offline support is disabled. (stripe out if not applicable)

Environment

Click To Expand

package.json:

{
  "name": "hi-zachary",
  "version": "1.0.0",
  "main": "expo-router/entry",
  "scripts": {
    "start": "expo start",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web"
  },
  "dependencies": {
    "@expo-google-fonts/dev": "^0.2.3",
    "@expo/vector-icons": "^14.0.2",
    "@op-engineering/op-sqlite": "^11.3.0",
    "@react-native-async-storage/async-storage": "1.23.1",
    "@react-native-community/netinfo": "11.4.1",
    "@stream-io/flat-list-mvcp": "^0.10.3",
    "@supabase/supabase-js": "^2.48.0",
    "expo": "^52.0.16",
    "expo-av": "^15.0.2",
    "expo-clipboard": "~7.0.1",
    "expo-constants": "~17.0.2",
    "expo-document-picker": "^13.0.2",
    "expo-file-system": "~18.0.7",
    "expo-font": "~13.0.3",
    "expo-haptics": "~14.0.1",
    "expo-image-manipulator": "~13.0.6",
    "expo-image-picker": "^16.0.4",
    "expo-linking": "~7.0.2",
    "expo-media-library": "^17.0.5",
    "expo-router": "~4.0.2",
    "expo-sharing": "^13.0.1",
    "expo-splash-screen": "~0.29.7",
    "expo-sqlite": "~15.0.6",
    "expo-status-bar": "~2.0.0",
    "expo-system-ui": "~4.0.7",
    "nativewind": "^4.1.23",
    "react": "18.3.1",
    "react-dom": "18.3.1",
    "react-native": "0.76.6",
    "react-native-gesture-handler": "~2.20.2",
    "react-native-quick-sqlite": "^8.2.7",
    "react-native-reanimated": "^3.16.7",
    "react-native-safe-area-context": "4.12.0",
    "react-native-screens": "~5.4.0",
    "react-native-svg": "15.8.0",
    "react-native-url-polyfill": "^2.0.0",
    "react-native-uuid": "^2.0.3",
    "react-native-web": "~0.19.6",
    "setimmediate": "^1.0.5",
    "stream-chat-expo": "^6.2.0",
    "tailwind-merge": "^2.6.0",
    "tailwindcss": "^3.4.17"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@types/react": "~18.3.12",
    "supabase": "^2.6.8",
    "typescript": "^5.7.3"
  },
  "resolutions": {
    "punycode": "1.4.1"
  },
  "private": true
}

react-native info output:

 OUTPUT GOES HERE

• Platform that you're experiencing the issue on:
  • [x] iOS

Additional context

here's an issue about the problem with expo: https://github.com/expo/expo/issues/29741

apparently using <Image /> from expo-image fixes it!

Screenshots

Click To Expand

---

[zfogg]

note my additional context:

here's an issue about the problem with expo: https://github.com/expo/expo/issues/29741

apparently using <Image /> from expo-image fixes it!

[khushal87]

Hey @zfogg, we have been testing this on expo 52 on our sample app with expo ~52.0.20, expo-media-library version 17.0.5 and expo-image-manipulator 13.0.6 and don't see any issue. Can you try out npx expo install --fix and rerun your app and see if that fixes your issue?

[khushal87]

Hey @zfogg, did the above fix solve your issue?

[khushal87]

Closing this issue due to a long time of inactivity and inability to reproduce it. Please feel free to reopen if you think its still reproducible after running npx expo install --fix. Thanks 😄

[itshenryx]

Hey, this issue still persists. I've tried running npx expo install --fix, but that's to no avail. Same exact issue as pointed out by OP.

[zfogg]

Hey @zfogg, did the above fix solve your issue?

i don't think it worked but i will test to be sure and update you.

[zfogg]

update: still doesn't work after npx expo install --fix and i get the same error.

looks like this:

[zfogg]

@khushal87 please reopen this issue. it's causing me trouble as i develop my product and i want to get this fixed so my users won't have errors when using my app

[khushal87]

Hey @zfogg, I am on:

 "expo": "~52.0.38",
"expo-image-picker": "^16.0.6",
"expo-media-library": "^17.0.6",
"expo-image-manipulator": "~13.0.6",
    "expo-router": "~4.0.19",
 "react-native": "0.76.7",
"stream-chat-expo":"6.7.0"

And I couldn't reproduce this issue. Please help us with a reproducible guide so that we can try it out on our side and help you with it. Thanks 😄

[zfogg]

i'll check my versions again and report back

[khushal87]

Also, by any chance, do you have anything on your application that we are unaware of? Old architecture? Enabled react compiler or some other customization in the SDK?

[itshenryx]

It this "usual" behavior on expo go?

[zfogg]

Also, by any chance, do you have anything on your application that we are unaware of? Old architecture? Enabled react compiler or some other customization in the SDK?

no i don't have any weird settings or anything like that. when i first reported this bug, i made sure to try and reproduce it from the most minimal project i could put together.

[itshenryx]

It this "usual" behavior on expo go?

@khushal87

[khushal87]

Hey team, it would be great if someone can provide us with a reproducible repository where we can reproduce this bug because on the versions mentioned above we haven't been able to repro this bug. It would be a great help and would be easy for us to triage and fix. Thanks :)

[sinameraji]

facing this issue in expo 53.

[khushal87]

Hey, I was able to reproduce it today on a bare Expo Go app. On the development build, this works just fine, and I can confirm that.

On Expo 53, you would ideally get the warning, which means you will have to create a development build to use the media library, and Expo Go will not work due to the change of permissions around Android policies.

Due to changes in Android's permission requirements, Expo Go can no longer provide full access to the media library. To test the full functionality of this module, you can create a development build. https://docs.expo.dev/develop/development-builds/create-a-build

I will close this issue because the expo team itself complains about it. Once they fix it, it should be fixed automatically for us as well.