https://github.com/g-ray/expo-router-content-link-issue
repro of issue opening a content: or other schemes with expo-router
https://github.com/g-ray/expo-router-content-link-issue
Last synced: about 1 year ago
JSON representation
repro of issue opening a content: or other schemes with expo-router
- Host: GitHub
- URL: https://github.com/g-ray/expo-router-content-link-issue
- Owner: G-Ray
- Created: 2023-08-06T21:28:31.000Z (almost 3 years ago)
- Default Branch: master
- Last Pushed: 2023-08-06T21:36:40.000Z (almost 3 years ago)
- Last Synced: 2025-02-15T02:25:50.506Z (over 1 year ago)
- Language: TypeScript
- Size: 252 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
It seems `expo-router` listens for any schemes/url.
This is an issue if you want to open `content:` schemes for instance.
```bash
npm i
```
Build the development app. You can run:
```bash
npm run build
adb push ./test.txt /sdcard/Download
adb push ./build-xxx.apk /sdcard/Download
```
Install the apk from the phone/emulator, then open `test.txt` from a file manager with the development app.
You will be redirected to a non existing screen.
Instead, I would expect being able to catch the `content:` url to handle the file programmatically.