Mac install error
See original GitHub issuenpm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-native-ble-plx@0.6.4 postinstall: node ./postinstall.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-native-ble-plx@0.6.4 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
If an error occurred while updating or installing macOS
If an error occurred while updating or installing macOS · Check your internet connection · Install in safe mode · Install after repairing...
Read more >How to Fix the "macOS Could Not Be Installed on Your ...
1. Restart Your Mac and Retry the Installation ... Sometimes, all you need to do to fix macOS errors is to restart your...
Read more >How to Fix macOS “Installation failed, An error occurred while ...
How To Fix The Installation Failed Error on macOS · Try Downloading The Update at Another Time · Reboot Your Mac · Make...
Read more >How to Fix 'macOS Could Not Be Installed on Your Computer ...
How to Fix the 'macOS Could Not Be Installed' Error · Restart and try the installation again. · Check the Date & Time...
Read more >9 Ways to Fix an Error Occurred While Preparing the Installation
Fix 1: Restart your Mac · Fix 2: Check the Date and Time · Fix 3: Boot Into Safe Mode · Fix 4:...
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
With new postinstall script I can see error message. Closing as it is not an issue of library itself. Hopefully with #29 we will be able to get rid of building issues once and for all.
From >=0.6.4 it should actually print the error message (in npm at least; yarn doesn’t print it in the console):