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

[expo-file-system] Error in upload : Location isn't readable #9281

Closed
srevolution opened this issue Jul 17, 2020 · 3 comments
Closed

[expo-file-system] Error in upload : Location isn't readable #9281

srevolution opened this issue Jul 17, 2020 · 3 comments

Comments

@srevolution
Copy link

srevolution commented Jul 17, 2020

Every time i try to upload an image with the function FileSystem.uploadAsync to my backend in localhost port 3333 , it gives me a error :

Location 'http://192.168.1.71:3333/upload' isn't readable.
- node_modules\react-native\Libraries\BatchedBridge\NativeModules.js:103:50 in promiseMethodWrapper
- node_modules\@unimodules\react-native-adapter\build\NativeModulesProxy.native.js:15:23 in moduleName.methodInfo.name
- node_modules\expo-file-system\build\FileSystem.js:114:17 in uploadAsync
- node_modules\regenerator-runtime\runtime.js:45:36 in tryCatch
- node_modules\regenerator-runtime\runtime.js:274:29 in invoke
- node_modules\regenerator-runtime\runtime.js:45:36 in tryCatch
- node_modules\regenerator-runtime\runtime.js:135:27 in invoke
- node_modules\regenerator-runtime\runtime.js:170:16 in PromiseImpl$argument_0
- node_modules\promise\setimmediate\core.js:45:6 in tryCallTwo
- node_modules\promise\setimmediate\core.js:200:22 in doResolve
- node_modules\promise\setimmediate\core.js:66:11 in Promise
- node_modules\regenerator-runtime\runtime.js:169:15 in callInvokeWithMethodAndArg
- node_modules\regenerator-runtime\runtime.js:192:38 in enqueue
- node_modules\regenerator-runtime\runtime.js:219:8 in exports.async
- node_modules\expo-file-system\build\FileSystem.js:110:7 in uploadAsync
* src\pages\camera\camera.js:135:17 in TouchableOpacity.props.onPress
- node_modules\regenerator-runtime\runtime.js:45:36 in tryCatch
- node_modules\regenerator-runtime\runtime.js:274:29 in invoke
- node_modules\regenerator-runtime\runtime.js:45:36 in tryCatch
- node_modules\regenerator-runtime\runtime.js:135:27 in invoke
- node_modules\regenerator-runtime\runtime.js:145:18 in PromiseImpl.resolve.then$argument_0
- node_modules\promise\setimmediate\core.js:37:13 in tryCallOne
- node_modules\promise\setimmediate\core.js:123:24 in setImmediate$argument_0
- node_modules\react-native\Libraries\Core\Timers\JSTimers.js:135:14 in _callTimer
- node_modules\react-native\Libraries\Core\Timers\JSTimers.js:183:16 in _callImmediatesPass
- node_modules\react-native\Libraries\Core\Timers\JSTimers.js:446:30 in callImmediates
* [native code]:null in callImmediates
- node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:396:6 in __callImmediates
- node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:373:10 in __guard
- node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:143:4 in flushedQueue
* [native code]:null in flushedQueue
* [native code]:null in invokeCallbackAndReturnFlushedQueue``

obs: SDK 38.0.0,
node:14.5.0

@barthap
Copy link
Contributor

barthap commented Jul 17, 2020

Can you make a reproducible demo? How do you call uploadAsync() - could you show code? Does it happen on Android, iOS, or both?

@NeOMakinG
Copy link

NeOMakinG commented Jul 18, 2020

#9076

Look like it's fixed by this, I think you can close it, methods signature of Android part was different than on iOS part

@barthap
Copy link
Contributor

barthap commented Jul 20, 2020

Yes, it is the same issue as in #9075 which is solved by #9076. Issue can be closed.

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

No branches or pull requests

5 participants