response error code: 500
See original GitHub issuereact-native, react and native-base version
0.46.0 15 2.2.0 windows10 Android
Expected behaviour
Actual behaviour
when I install it via npm install native-base
then react-native link
and react-native run-android
then react-native start
The development server returned response error code: 500
URL: http://10.0.2.2:8081/index.android.bundle?platform=android&dev=true&hot=true&minify=false
Body:
{"from":"C:\\Users\\user\\ex\\node_modules\\native-base\\dist\\src\\Utils\\computeProps.js","to":"react-native/Libraries/Renderer/src/renderers/native/ReactNativePropRegistry","message":"Unable to resolve module `react-native/Libraries/Renderer/src/renderers/native/ReactNativePropRegistry` from `C:\\Users\\user\\ex\\node_modules\\native-base\\dist\\src\\Utils\\computeProps.js`: Module does not exist in the module map\n\nThis might be related to https://github.com/facebook/react-native/issues/4968\nTo resolve try the following:\n 1. Clear watchman watches: `watchman watch-del-all`.\n 2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.\n 3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start -- --reset-cache`.","name":"UnableToResolveError","type":"UnableToResolveError","errors":[{}]}
processBundleResult
BundleDownloader.java:172
access$100
BundleDownloader.java:38
execute
BundleDownloader.java:108
emitChunk
MultipartStreamReader.java:69
readAllParts
MultipartStreamReader.java:116
onResponse
BundleDownloader.java:96
execute
RealCall.java:135
run
NamedRunnable.java:32
runWorker
ThreadPoolExecutor.java:1162
run
ThreadPoolExecutor.java:636
run
Thread.java:764
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:12 (2 by maintainers)
Top Results From Across the Web
500 Internal Server Error - HTTP - MDN Web Docs - Mozilla
This error response is a generic "catch-all" response. Usually, this indicates the server cannot find a better 5xx error code to response.
Read more >HTTP 500 Internal Server Error: What It Means & How to Fix It
This is an HTTP response status code error. It tells you that a web browser wants to access your web page and your...
Read more >HTTP Status Code 500: What Is the 500 "Internal Server Error"?
The 500 status code "internal server error" is just that - it's an error on the server-side. This means that the server encountered...
Read more >How to fix HTTP 500 internal server error? - IONOS
The “Internal Server Error” can occur when the request is processed by the web server. The collective status code includes everything unplanned ...
Read more >How to Fix a 500 Internal Server Error - Lifewire
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the website's server, but...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can finally git rid this error by doing this
replace
react-native/Libraries/Renderer/src/renderers/native/ReactNativePropRegistry
withreact-native/Libraries/Renderer/shims/ReactNativePropRegistry
on
node_modules\native-base\dist\src\Utils\computeProps.js
andnode_modules\react-native-easy-grid\Utils\computeProps.js
Thanks to @deathemperor and @ajostergaard
For a temporary solution while waiting for official fix, you can edit the file:
node_modules\native-base\dist\src\Utils\computeProps.js
, replace:react-native/Libraries/Renderer/src/renderers/native/ReactNativePropRegistry
WITHreact-native/Libraries/Renderer/shims/ReactNativePropRegistry