Failed to install expo package with error npm exited with non zero code 1

Im currently trying to update my Expo SDK from 36.0.0 to atleast 37.0.0 with the command expo update
however im getting the error:

  × Failed to install expo package with error: yarnpkg exited with non-zero code: 1
yarnpkg exited with non-zero code: 1
Error: yarnpkg exited with non-zero code: 1
    at ChildProcess.completionListener (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:65:13)
    at Object.onceWrapper (events.js:422:26)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.cp.emit (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modulescross-spawnlibenoent.js:34:29)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
    ...
    at Object.spawnAsync [as default] (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:26:19)
    at YarnPackageManager._runAsync (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:288:31)
    at YarnPackageManager.addAsync (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:241:16)
    at upgradeAsync (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clisrccommandsupgrade.ts:465:5)
    at C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clisrccommandsupgrade.ts:701:7
    at Command.<anonymous> (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clisrcexp.ts:302:7)

npm version : 6.14.8
yarn version : 2.2.2 i also tried it with a lower version 1.x.x
expo diagnostics :

 Expo CLI 3.27.4 environment info:
    System:
      OS: Windows 10 10.0.19041
    Binaries:
      Node: 12.18.3 - C:Program Filesnodejsnode.EXE
      Yarn: 2.2.2 - C:UsersPhilippAppDataRoamingnpmyarn.CMD
      npm: 6.14.8 - C:Program Filesnodejsnpm.CMD
    npmPackages:
      expo: ^36.0.0 => 36.0.2
      react: 16.9.0 => 16.9.0
      react-dom: 16.9.0 => 16.9.0
      react-native: https://github.com/expo/react-native/archive/sdk-36.0.1.tar.gz => 0.61.4
      react-native-web: ^0.11.7 => 0.11.7
      react-navigation: 3.11.1 => 3.11.1
    Expo Workflow: managed

Hopefully someone can help me, any help is appreciated. Thank you very much!

EXPO SDK 45 BETA — error running upgrade — failed to install expo package expo@next #17257

Summary

I run «EXPO_BETA=1 expo upgrade» and get the following output:
I’m on expo sdk 44 and trying to run the expo 45 beta upgrade and it starts to install the expo@next package then bombs with the following error:

✔️ Would you like to proceed? … yes

✔️ You are currently using SDK 44.0.0. Would you like to update to the latest version, 45.0.0? … yes

⠦ Installing the expo@next package…

✖️ Failed to install expo package with error: yarnpkg exited with signal: SIGABRT
yarnpkg exited with signal: SIGABRT
Error: yarnpkg exited with signal: SIGABRT
at ChildProcess.completionListener (/Users/soleary/.config/yarn/global/node_modules/@expo/spawn-async/src/spawnAsync.ts:64:13)
at Object.onceWrapper (events.js:520:26)
at ChildProcess.emit (events.js:400:28)
at maybeClose (internal/child_process.js:1055:16)
at Socket. (internal/child_process.js:441:11)
at Socket.emit (events.js:400:28)
at Pipe. (net.js:675:12)
…
at spawnAsync (/Users/soleary/.config/yarn/global/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
at YarnPackageManager._runAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:327:31)
at YarnPackageManager.addWithParametersAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:272:16)
at YarnPackageManager.addAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:276:5)
at upgradeAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:496:7)
at actionAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:42:3)

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

expo-env-info 1.0.3 environment info:
System:
OS: macOS 11.6.5
Shell: 5.8 — /bin/zsh
Binaries:
Node: 14.17.6 — /usr/local/bin/node
Yarn: 1.22.15 —

/.yarn/bin/yarn
npm: 6.14.15 — /usr/local/bin/npm
Watchman: 2021.09.27.00 — /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 — /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 25, 26, 27, 28, 29, 30
Build Tools: 29.0.2, 29.0.3, 30.0.3, 31.0.0
System Images: android-28 | Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.6 AI-192.7142.36.36.6241897
Xcode: 12.4/12D4e — /usr/bin/xcodebuild
npmPackages:
@expo/webpack-config:

0.16.2 => 0.16.18
babel-preset-expo: 9.0.2 => 9.0.2
expo: ^44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
expo-cli: 5.4.3
Expo Workflow: managed

Reproducible demo

The text was updated successfully, but these errors were encountered:

Источник

Using EXPO_BETA=1 expo upgrade when no beta release is available has unexpected behavior #4082

Summary

× Failed to install expo package with error: yarnpkg exited with non-zero code: 1

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

Expo CLI 5.0.1 environment info:
System:
OS: Windows 10 10.0.19042
Binaries:
Node: 16.13.1 — C:Program Filesnodejsnode.EXE
Yarn: 1.22.17 —

AppDataRoamingnpmyarn.CMD
npm: 8.1.2 — C:Program Filesnodejsnpm.CMD
SDKs:
Android SDK:
API Levels: 28, 29, 30, 31
Build Tools: 28.0.3, 29.0.2, 30.0.2, 31.0.0
System Images: android-30 | Google APIs Intel x86 Atom
IDEs:
Android Studio: Version 4.2.0.0 AI-202.7660.26.42.7486908
npmPackages:
babel-preset-expo: 8.5.1 => 8.5.1
expo: ^43.0.0 => 43.0.3
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: https://github.com/expo/react-native/archive/sdk-43.tar.gz => 0.64.3
react-native-web: 0.17.1 => 0.17.1
Expo Workflow: managed

Reproducible demo

yarnpkg exited with non-zero code: 1
Error: yarnpkg exited with non-zero code: 1
at ChildProcess.completionListener (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:65:13)
at Object.onceWrapper (node:events:510:26)
at ChildProcess.emit (node:events:390:28)
at ChildProcess.cp.emit (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modulescross-spawnlibenoent.js:34:29)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
.
at Object.spawnAsync [as default] (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:26:19)
at YarnPackageManager._runAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:309:31)
at YarnPackageManager.addAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:258:16)
at upgradeAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clisrccommandsinfoupgradeAsync.ts:496:7)
at actionAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clisrccommandsinfoupgradeAsync.ts:42:3)

The text was updated successfully, but these errors were encountered:

Источник

expo install firebase errors, npm install firebase doesn’t #3066

Description

Installing the Firebase module fails using expo install firebase , works using npm install firebase on Windows 8 and 10.

Environment

0.13.12 => 0.13.18 Expo Workflow: managed»>

Expected Behavior

In a fresh Expo project, I do

I expect Firebase to install successfully.

Observed Behavior

An error happens and Firebase fails to install. Here’s the error output.

Reproducible Demo

Create a fresh Expo app, try to install Firebase with the Expo CLI. Note: this dumps many C compilation warnings dumped to foo.txt.

The following does NOT have an error. No compilation warnings appear either.

The text was updated successfully, but these errors were encountered:

I’m having the same issue, but doing yarn add firebase@7.9.0 , which the version selected by Expo, also fails.
So to avoid this, two possibilities:

• either Expo updates to version ^8
• or we fix building firebase@7.9.0

(I’m having issues with Expo+Firebase 8, not sure if downgrading to 7.9.0 would fix it).

Got it to work by downgrading to Node.js 10.16.0 !

im also having the same problem.

I m trying to solve this problem for the last 2 days but no result

For me and some students, it worked to let npm install the current Firebase, rather than the version Expo wants to install.

I encountered the same problem . Who knows the solution? use npm install firebase instead of expo install firebase ?

Thank you @nathanvogel. I have been trying from two days. Your comment helped me.

Same issue, and resolved by just downloading the latest version of firebase. Is there a way the expo install command can be updated to skip this version?

Got it to work by downgrading to Node.js 10.16.0 !

yep done and working

Can we get a dev or project manager to weigh in and set expectations? This seems rather significant if Firebase is practically unusable in Expo. I say practically because downgrading to a version of Node that is nearly 3 years old and about to leave maintenance doesn’t seem practical.

@jojenki — we have bumped the supported firebase js version in sdk 41 but left things as-is in sdk 40. this is a result of changes in the ecosystem that have occurred since we released sdk 40, in particular the native dependency firebase@7.9.0 has on grpc and the interaction with that and certain node versions / development machine configurations.

you can install firebase@8.2.3 in your sdk 40 project and it will work as expected, but you will get a warning about it not being the suggested version.

Yes, installing firebase with npm rather than expo worked for me, except for the warning from Expo.

Thanks for the quick response. I’m running into a related but separate error, it seems, so I’ll open a separate issue for that.

@jojenki — we have bumped the supported firebase js version in sdk 41 but left things as-is in sdk 40. this is a result of changes in the ecosystem that have occurred since we released sdk 40, in particular the native dependency firebase@7.9.0 has on grpc and the interaction with that and certain node versions / development machine configurations.

you can install firebase@8.2.3 in your sdk 40 project and it will work as expected, but you will get a warning about it not being the suggested version.

works for me thanks you..

Some dependencies are incompatible with the installed expo package version:

• firebase — expected version range: 8.2.3 — actual version installed: ^8.4.1

Firebase updated yet expo didn’t? Why..
Running:
expo install firebase@8.2.3
Worked for me but why downgrading pehh.

@LOTRAudition — you don’t have to downgrade necessarily, if you want to just ignore the warning and the newer version works for you then it’s fine. but we only test against the expected version, and it is not uncommon for new firebase js releases to break compatibility with react-native

expo sdk 41 tests against and recommends firebase@8.2.3, which resolves the original issue topic, so i’m closing this

npm install firebase
worked for me. Thanks guys

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

build failing with «yarn exited with non-zero code: 1» #15172

Summary

My eas cloud builds are failing with the following error: «yarn exited with non-zero code: 1» for both android and iOS.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

Expo CLI 4.13.0 environment info:
System:
OS: macOS 11.6
Shell: 5.8 — /bin/zsh
Binaries:
Node: 16.13.0 — /usr/local/bin/node
Yarn: 1.22.15 —

/.yarn/bin/yarn
npm: 8.1.0 — /usr/local/bin/npm
Watchman: 2021.10.04.00 — /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 — /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.6858069
Xcode: 13.1/13A1030d — /usr/bin/xcodebuild
npmPackages:
expo:

43.0.0 => 43.0.2
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
expo-cli: 4.13.0
Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

I don’t have a reproducible repo for this yet, I am creating it but just wanted to submit the issue incase its a quick and easy fix.

The text was updated successfully, but these errors were encountered:

Источник

Expo Init Error with error code 1 #318

Description

Currently I am trying to start developing a React-Native Application by following the tutorial on its official website, https://facebook.github.io/react-native/docs/getting-started. As a reach step 2, which is initializing the project by calling expo init AwesomeProject , I encountered an error during the initialization when it is installing dependencies.

Expected Behavior

The expected behavior for this is successfully finish running without encountering any error, and allow me to continue on with the tutorial process.

Observed Behavior

An error log is generated with exit status 1.

Environment

Reproducible Demo

1. Update Node to the latest version 10.15.0
2. Update Npm to the latest version 6.6.0
3. Install Expo by executing npm install -g expo-cli
4. Run expo init AwesomeProject and the error will appear

The text was updated successfully, but these errors were encountered:

Facing similar issue . macOS Mojave ( 10.14.2). Node version : v10.15.1, npm version : 6.4.1.
Installed expo-cli through bellow command.

creating new project «AwesomeProject»:

? Choose a template: expo-template-blank
? Choose which workflow to use: managed
✔ Please enter a few initial configuration values.
Read more: https://docs.expo.io/versions/latest/workflow/configuration · 100% completed
[14:11:59] Extracting project files.
[14:12:00] Customizing project.
[14:12:03] Initialized a git repository.
[14:12:03] Installing dependencies.
npm ERR! code 1
npm ERR! Command failed: /usr/bin/git clone —depth=1 -q -b v0.22.1-exp.0 git://github.com/expo/react-native-maps.git /Users/a1/.npm/_cacache/tmp/git-clone-0bb1cd6d
npm ERR! /Users/a1/.npm/_cacache/tmp/git-clone-0bb1cd6d/.git: Permission denied
npm ERR!

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/a1/.npm/_logs/2019-02-19T08_42_32_124Z-debug.log
[14:12:32] Process exited with non-zero code: 1
[14:12:32] Set EXPO_DEBUG=true in your env to view the stack trace.

Источник

Hi, just ran into the same issue

- Installing the expo@^45.0.0 package...
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...

<--- Last few GCs --->

[53703:0x7f82b0008000]   122534 ms: Scavenge 4036.5 (4120.1) -> 4034.3 (4123.8) MB, 24.3 / 0.0 ms  (average mu = 0.512, current mu = 0.320) allocation failure
[53703:0x7f82b0008000]   122563 ms: Scavenge 4039.8 (4123.8) -> 4037.1 (4141.3) MB, 12.5 / 0.0 ms  (average mu = 0.512, current mu = 0.320) allocation failure
[53703:0x7f82b0008000]   124404 ms: Mark-sweep 4049.8 (4141.3) -> 4041.8 (4149.8) MB, 1798.3 / 0.0 ms  (average mu = 0.336, current mu = 0.122) allocation failure scavenge
might not succeed


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x10d6d6324 node::Abort() [/usr/local/Cellar/node@16/16.15.1/bin/node]
 2: 0x10d6d64a6 node::OnFatalError(char const*, char const*) [/usr/local/Cellar/node@16/16.15.1/bin/node]
 3: 0x10d817d85 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/Cellar/node@16/16.15.1/bin/node]
 4: 0x10d817d2f v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/Cellar/node@16/16.15.1/bin/node]
 5: 0x10d940bdb v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/Cellar/node@16/16.15.1/bin/node]
 6: 0x10d93fc5b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/Cellar/node@16/16.
15.1/bin/node]
 7: 0x10d948231 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment)
[/usr/local/Cellar/node@16/16.15.1/bin/node]
 8: 0x10d948292 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment)
 [/usr/local/Cellar/node@16/16.15.1/bin/node]
 9: 0x10d9256f7 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/local/Cellar/node@16/16.15.1/bin/node]
10: 0x10dbbb7ca v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/local/Cellar/node@16/16.15.1/bin/node]
11: 0x10de526b9 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/usr/local/Cellar/node@16/16.15.1/bin/node]
✖ Failed to install expo package with error: yarnpkg exited with signal: SIGABRT
yarnpkg exited with signal: SIGABRT
Error: yarnpkg exited with signal: SIGABRT
    at ChildProcess.completionListener (.../node_modules/@expo/spawn-async/src/spawnAsync.ts:64:13)
    at Object.onceWrapper (node:events:642:26)
    at ChildProcess.emit (node:events:527:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Socket.<anonymous> (node:internal/child_process:451:11)
    at Socket.emit (node:events:527:28)
    at Pipe.<anonymous> (node:net:709:12)
    ...
    at spawnAsync (…/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
    at YarnPackageManager._runAsync .../node_modules/@expo/package-manager/src/NodePackageManagers.ts:314:31)
    at YarnPackageManager.addWithParametersAsync (.../node_modules/@expo/package-manager/src/NodePackageManagers.ts:259:16)
    at YarnPackageManager.addAsync (…/node_modules/@expo/package-manager/src/NodePackageManagers.ts:263:5)
    at upgradeAsync (…/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:496:7)
    at actionAsync (…/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:42:3)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I tried with

NODE_OPTIONS=--max_old_space_size=16384 EXPO_DEBUG=true expo upgrade

and still no luck ☹

I tried yarn upgrade @babel/core before doing it again, and it worked!

Using EXPO_BETA=1 expo upgrade when no beta release is available has unexpected behavior #4082

Comments

ahmetbasdan commented Dec 18, 2021

Summary

× Failed to install expo package with error: yarnpkg exited with non-zero code: 1

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

Expo CLI 5.0.1 environment info:
System:
OS: Windows 10 10.0.19042
Binaries:
Node: 16.13.1 — C:Program Filesnodejsnode.EXE
Yarn: 1.22.17 —

AppDataRoamingnpmyarn.CMD
npm: 8.1.2 — C:Program Filesnodejsnpm.CMD
SDKs:
Android SDK:
API Levels: 28, 29, 30, 31
Build Tools: 28.0.3, 29.0.2, 30.0.2, 31.0.0
System Images: android-30 | Google APIs Intel x86 Atom
IDEs:
Android Studio: Version 4.2.0.0 AI-202.7660.26.42.7486908
npmPackages:
babel-preset-expo: 8.5.1 => 8.5.1
expo: ^43.0.0 => 43.0.3
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: https://github.com/expo/react-native/archive/sdk-43.tar.gz => 0.64.3
react-native-web: 0.17.1 => 0.17.1
Expo Workflow: managed

Reproducible demo

yarnpkg exited with non-zero code: 1
Error: yarnpkg exited with non-zero code: 1
at ChildProcess.completionListener (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:65:13)
at Object.onceWrapper (node:events:510:26)
at ChildProcess.emit (node:events:390:28)
at ChildProcess.cp.emit (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modulescross-spawnlibenoent.js:34:29)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
.
at Object.spawnAsync [as default] (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:26:19)
at YarnPackageManager._runAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:309:31)
at YarnPackageManager.addAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:258:16)
at upgradeAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clisrccommandsinfoupgradeAsync.ts:496:7)
at actionAsync (C:UsersahmetAppDataRoamingnpmnode_modulesexpo-clisrccommandsinfoupgradeAsync.ts:42:3)

The text was updated successfully, but these errors were encountered:

Источник

build failing with «yarn exited with non-zero code: 1» #15172

Comments

haibert commented Nov 12, 2021 •

Summary

My eas cloud builds are failing with the following error: «yarn exited with non-zero code: 1» for both android and iOS.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

Expo CLI 4.13.0 environment info:
System:
OS: macOS 11.6
Shell: 5.8 — /bin/zsh
Binaries:
Node: 16.13.0 — /usr/local/bin/node
Yarn: 1.22.15 —

/.yarn/bin/yarn
npm: 8.1.0 — /usr/local/bin/npm
Watchman: 2021.10.04.00 — /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 — /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.6858069
Xcode: 13.1/13A1030d — /usr/bin/xcodebuild
npmPackages:
expo:

43.0.0 => 43.0.2
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
expo-cli: 4.13.0
Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

I don’t have a reproducible repo for this yet, I am creating it but just wanted to submit the issue incase its a quick and easy fix.

The text was updated successfully, but these errors were encountered:

Источник

EXPO SDK 45 BETA — error running upgrade — failed to install expo package expo@next #17257

Comments

sean-m-oleary commented Apr 28, 2022 •

Summary

I run «EXPO_BETA=1 expo upgrade» and get the following output:
I’m on expo sdk 44 and trying to run the expo 45 beta upgrade and it starts to install the expo@next package then bombs with the following error:

✔️ Would you like to proceed? … yes

✔️ You are currently using SDK 44.0.0. Would you like to update to the latest version, 45.0.0? … yes

⠦ Installing the expo@next package…

✖️ Failed to install expo package with error: yarnpkg exited with signal: SIGABRT
yarnpkg exited with signal: SIGABRT
Error: yarnpkg exited with signal: SIGABRT
at ChildProcess.completionListener (/Users/soleary/.config/yarn/global/node_modules/@expo/spawn-async/src/spawnAsync.ts:64:13)
at Object.onceWrapper (events.js:520:26)
at ChildProcess.emit (events.js:400:28)
at maybeClose (internal/child_process.js:1055:16)
at Socket. (internal/child_process.js:441:11)
at Socket.emit (events.js:400:28)
at Pipe. (net.js:675:12)
…
at spawnAsync (/Users/soleary/.config/yarn/global/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
at YarnPackageManager._runAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:327:31)
at YarnPackageManager.addWithParametersAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:272:16)
at YarnPackageManager.addAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:276:5)
at upgradeAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:496:7)
at actionAsync (/Users/soleary/.config/yarn/global/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:42:3)

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

expo-env-info 1.0.3 environment info:
System:
OS: macOS 11.6.5
Shell: 5.8 — /bin/zsh
Binaries:
Node: 14.17.6 — /usr/local/bin/node
Yarn: 1.22.15 —

/.yarn/bin/yarn
npm: 6.14.15 — /usr/local/bin/npm
Watchman: 2021.09.27.00 — /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 — /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 25, 26, 27, 28, 29, 30
Build Tools: 29.0.2, 29.0.3, 30.0.3, 31.0.0
System Images: android-28 | Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.6 AI-192.7142.36.36.6241897
Xcode: 12.4/12D4e — /usr/bin/xcodebuild
npmPackages:
@expo/webpack-config:

0.16.2 => 0.16.18
babel-preset-expo: 9.0.2 => 9.0.2
expo: ^44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
expo-cli: 5.4.3
Expo Workflow: managed

Reproducible demo

The text was updated successfully, but these errors were encountered:

Источник

Failed to build standalone app err: Error: yarn exited with non-zero code: 1 #216

Comments

almoret commented May 1, 2020 •

Im trying to build an apk file, but im facing the following error:

May 1 10:47:10 turtle[14551] ERROR: Failed to build standalone app
err: Error: yarn exited with non-zero code: 1
at ChildProcess.completionListener (/usr/local/lib/node_modules/turtle-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:65:13)
at Object.onceWrapper (events.js:286:20)
at ChildProcess.emit (events.js:198:13)
at ChildProcess.EventEmitter.emit (domain.js:448:20)
at maybeClose (internal/child_process.js:982:16)
at Socket.stream.socket.on (internal/child_process.js:389:11)
at Socket.emit (events.js:198:13)
at Socket.EventEmitter.emit (domain.js:448:20)
at Pipe._handle.close (net.js:606:12)
.
at spawnAsync (/usr/local/lib/node_modules/turtle-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
at Object.spawnAsyncThrowError (/@expo/xdl@57.8.30/src/detach/ExponentTools.ts 💯 19)
at _installNodeModules (/usr/local/lib/node_modules/turtle-cli/src/bin/setup/android/index.ts:106:23)
platform: «android»
MacBook-Air-de-Alex:react-new-app alexmoret$ expo diagnostics

Expo CLI 3.20.1 environment info:
System:
OS: macOS 10.15.3
Shell: 3.2.57 — /bin/bash
Binaries:
Node: 10.16.0 — /usr/local/bin/node
Yarn: 1.17.3 — /usr/local/bin/yarn
npm: 6.14.4 — /usr/local/bin/npm
IDEs:
Xcode: 11.3.1/11C504 — /usr/bin/xcodebuild
npmPackages:
expo: ^37.0.0 => 37.0.7
react: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.0.tar.gz => 0.61.4
npmGlobalPackages:
expo-cli: 3.20.1

Can, anyone, help me?

The text was updated successfully, but these errors were encountered:

dsokal commented May 4, 2020

Hi @almoret,
Could you please share the whole log output (look at the issue template)? The logline you posted is too generic to help you.

almoret commented May 4, 2020 •

Thanks! Here is the whole log output

The manifest URL is: https://exp.host/@labmoonwalk/temakeria (​https://exp.host/@labmoonwalk/temakeria/index.exp?sdkVersion=37.0.0​). Learn more. (​https://expo.fyi/manifest-url​)
The project page is: https://expo.io/@labmoonwalk/temakeria (​https://expo.io/@labmoonwalk/temakeria​). Learn more. (​https://expo.fyi/project-page​)
MacBook-Air-de-Alex:react-new-app alexmoret$ export EXPO_USERNAME=XXXXXXXXX
MacBook-Air-de-Alex:react-new-app alexmoret$ export EXPO_PASSWORD=XXXXXXX
MacBook-Air-de-Alex:react-new-app alexmoret$ export EXPO_ANDROID_KEYSTORE_PASSWORD=XXXXXXXX
MacBook-Air-de-Alex:react-new-app alexmoret$ export EXPO_ANDROID_KEY_PASSWORD=XXXXXXXX
MacBook-Air-de-Alex:react-new-app alexmoret$ turtle build:android —keystore-path credentials/carambolah.keystore -t apk —keystore-alias br.com.moonwalk.temakeriaecia
May 4 09:35:10 turtle[1485] INFO: shell app for SDK 37.0.0 doesn’t exist, downloading.
platform: «android»
buildPhase: «setting up environment»
downloading [=================== ] 95% 0.7sMay 4 09:35:24 turtle[1485] INFO: shell app has been downloaded
platform: «android»
buildPhase: «setting up environment»
May 4 09:35:24 turtle[1485] INFO: extracting shell app (this may take a while).
platform: «android»
buildPhase: «setting up environment»
May 4 09:35:28 turtle[1485] INFO: shell app extracted
platform: «android»
buildPhase: «setting up environment»
May 4 09:35:28 turtle[1485] INFO: installing dependencies in /Users/alexmoret/.turtle/workingdir/android/sdk37 directory.
platform: «android»
buildPhase: «setting up environment»
May 4 09:35:29 turtle[1485] INFO: yarn install v1.17.3
platform: «android»
buildPhase: «setting up environment»
source: «stdout»
May 4 09:35:29 turtle[1485] INFO: info No lockfile found.
platform: «android»
buildPhase: «setting up environment»
source: «stdout»
May 4 09:35:29 turtle[1485] INFO: [1/4] Resolving packages.
platform: «android»
buildPhase: «setting up environment»
source: «stdout»
May 4 09:35:43 turtle[1485] INFO: warning expo-cli > babel-runtime > core-js@2.6.11: core-js@ @expo/xdl > joi@14.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:50 turtle[1485] INFO: warning expo-cli > @expo/xdl > joi > hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:50 turtle[1485] INFO: warning expo-cli > @expo/xdl > joi > topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:50 turtle[1485] INFO: warning expo-cli > @expo/xdl > joi > topo > hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:50 turtle[1485] INFO: warning expo-cli > @expo/xdl > @expo/ngrok > request@2.88.2: request has been deprecated, see request/request#3142
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:50 turtle[1485] INFO: warning expo-cli > @expo/xdl > probe-image-size > request@2.88.2: request has been deprecated, see request/request#3142
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:50 turtle[1485] INFO: warning expo-cli > pacote > @npmcli/run-script > node-gyp > request@2.88.2: request has been deprecated, see request/request#3142
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:53 turtle[1485] INFO: warning expo-cli > @expo/xdl > webpack-dev-server > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:54 turtle[1485] INFO: warning expo-cli > @expo/xdl > webpack > watchpack > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:57 turtle[1485] INFO: warning expo-cli > @expo/xdl > @expo/webpack-config > react-dev-utils > fork-ts-checker-webpack-plugin > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:59 turtle[1485] INFO: warning expo-cli > @expo/xdl > @expo/webpack-config > workbox-webpack-plugin > workbox-build > joi@11.4.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:59 turtle[1485] INFO: warning expo-cli > @expo/xdl > @expo/webpack-config > workbox-webpack-plugin > workbox-build > joi > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:59 turtle[1485] INFO: warning expo-cli > @expo/xdl > @expo/webpack-config > workbox-webpack-plugin > workbox-build > joi > topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:35:59 turtle[1485] INFO: warning expo-cli > @expo/xdl > @expo/webpack-config > workbox-webpack-plugin > workbox-build > joi > topo > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:01 turtle[1485] INFO: warning expo-cli > @expo/xdl > webpack-dev-server > chokidar > fsevents@1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:06 turtle[1485] INFO: warning expo-cli > @expo/package-manager > find-yarn-workspace-root > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:06 turtle[1485] INFO: warning expo-cli > @expo/package-manager > find-yarn-workspace-root > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:17 turtle[1485] INFO: warning workspace-aggregator-99a1fb5a-7037-44de-a721-da8feca6574f > expo-module-scripts > @babel/cli > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:18 turtle[1485] INFO: warning workspace-aggregator-99a1fb5a-7037-44de-a721-da8feca6574f > expo-ads-facebook > fbemitter > fbjs > core-js@1.2.7: core-js@ jest-expo-puppeteer > babel-jest > @jest/transform > jest-haste-map > fsevents@1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:22 turtle[1485] INFO: warning workspace-aggregator-99a1fb5a-7037-44de-a721-da8feca6574f > jest-expo-enzyme > jest-enzyme > jest-environment-enzyme > jest-environment-jsdom > jsdom > request@2.88.2: request has been deprecated, see request/request#3142
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:23 turtle[1485] INFO: warning workspace-aggregator-99a1fb5a-7037-44de-a721-da8feca6574f > jest-expo-puppeteer > jest-puppeteer > jest-environment-puppeteer > jest-dev-server > wait-on > core-js@2.6.11: core-js@ jest-expo-puppeteer > jest-puppeteer > jest-environment-puppeteer > jest-dev-server > wait-on > request@2.88.2: request has been deprecated, see request/request#3142
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:24 turtle[1485] INFO: warning workspace-aggregator-99a1fb5a-7037-44de-a721-da8feca6574f > jest-expo-enzyme > jest-enzyme > jest-environment-enzyme > jest-environment-jsdom > jsdom > left-pad@1.3.0: use String.prototype.padStart()
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:27 turtle[1485] INFO: [2/4] Fetching packages.
platform: «android»
buildPhase: «setting up environment»
source: «stdout»
May 4 09:36:31 turtle[1485] INFO: info @expo/traveling-fastlane-linux@1.13.1: The platform «darwin» is incompatible with this module.
platform: «android»
buildPhase: «setting up environment»
source: «stdout»
May 4 09:36:31 turtle[1485] INFO: info «@expo/traveling-fastlane-linux@1.13.1» is an optional dependency and failed compatibility check. Excluding it from installation.
platform: «android»
buildPhase: «setting up environment»
source: «stdout»
May 4 09:36:31 turtle[1485] INFO: error move-file@2.0.0: The engine «node» is incompatible with this module. Expected version «>=10.17». Got «10.16.0»
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:31 turtle[1485] INFO: error Found incompatible module.
platform: «android»
buildPhase: «setting up environment»
source: «stderr»
May 4 09:36:31 turtle[1485] INFO: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
platform: «android»
buildPhase: «setting up environment»
source: «stdout»
May 4 09:36:31 turtle[1485] ERROR: Failed to build standalone app
err: Error: yarn exited with non-zero code: 1
at ChildProcess.completionListener (/usr/local/lib/node_modules/turtle-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:65:13)
at Object.onceWrapper (events.js:286:20)
at ChildProcess.emit (events.js:198:13)
at ChildProcess.EventEmitter.emit (domain.js:448:20)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
.
at spawnAsync (/usr/local/lib/node_modules/turtle-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
at Object.spawnAsyncThrowError (/@expo/xdl@57.8.30/src/detach/ExponentTools.ts 💯 19)
at _installNodeModules (/usr/local/lib/node_modules/turtle-cli/src/bin/setup/android/index.ts:106:23)
platform: «android»

dsokal commented May 4, 2020

The engine «node» is incompatible with this module. Expected version «>=10.17». Got «10.16.0»
This is the culprit. Try upgrading node to at least 10.17.

almoret commented May 4, 2020

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Im currently trying to update my Expo SDK from 36.0.0 to atleast 37.0.0 with the command expo update
however im getting the error:

  × Failed to install expo package with error: yarnpkg exited with non-zero code: 1
yarnpkg exited with non-zero code: 1
Error: yarnpkg exited with non-zero code: 1
    at ChildProcess.completionListener (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:65:13)
    at Object.onceWrapper (events.js:422:26)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.cp.emit (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modulescross-spawnlibenoent.js:34:29)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
    ...
    at Object.spawnAsync [as default] (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:26:19)
    at YarnPackageManager._runAsync (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:288:31)
    at YarnPackageManager.addAsync (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:241:16)
    at upgradeAsync (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clisrccommandsupgrade.ts:465:5)
    at C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clisrccommandsupgrade.ts:701:7
    at Command.<anonymous> (C:UsersPhilippAppDataRoamingnpmnode_modulesexpo-clisrcexp.ts:302:7)

npm version : 6.14.8
yarn version : 2.2.2 i also tried it with a lower version 1.x.x
expo diagnostics :

 Expo CLI 3.27.4 environment info:
    System:
      OS: Windows 10 10.0.19041
    Binaries:
      Node: 12.18.3 - C:Program Filesnodejsnode.EXE
      Yarn: 2.2.2 - C:UsersPhilippAppDataRoamingnpmyarn.CMD
      npm: 6.14.8 - C:Program Filesnodejsnpm.CMD
    npmPackages:
      expo: ^36.0.0 => 36.0.2
      react: 16.9.0 => 16.9.0
      react-dom: 16.9.0 => 16.9.0
      react-native: https://github.com/expo/react-native/archive/sdk-36.0.1.tar.gz => 0.61.4
      react-native-web: ^0.11.7 => 0.11.7
      react-navigation: 3.11.1 => 3.11.1
    Expo Workflow: managed

Hopefully someone can help me, any help is appreciated. Thank you very much!

I’m following a tutorial requiring installing firebase specifically through expo, I get this error every time, is there an obvious fix to this i’m not seeing?

Terminal:

expo install firebase

Installing 1 SDK 40.0.0 compatible native module using npm.

> npm install

> grpc@1.24.2 install C:\\node_modulesgrpc

> node-pre-gyp install —fallback-to-build —library=static_library

node-pre-gyp WARN Using needle for node-pre-gyp https download

node-pre-gyp WARN Tried to download(404): https://node-precompiled-binaries.grpc.io/grpc/v1.24.2/node-v83-win32-x64-unknown.tar.gz

node-pre-gyp WARN Pre-built binaries not found for grpc@1.24.2 and node@14.13.0 (node-v83 ABI, unknown) (falling back to source compile with node-gyp)

gyp ERR! find Python

gyp ERR! find Python Python is not set from command line or npm configuration

gyp ERR! find Python Python is not set from environment variable PYTHON

gyp ERR! find Python checking if «python» can be used

gyp ERR! find Python — «python» is not in PATH or produced an error

Failed to execute ‘C:Program Filesnodejsnode.exe C:Program Filesnodejsnode_modulesnpmnode_modulesnode-gypbinnode-gyp.js configure —fallback-to-build —library=static_library —module=C:\\\\\srcnodeextension_binarynode-v83-win32-x64-unknowngrpc_node.node —module_name=grpc_node —module_path=C:\\\\grpcsrcnodeextension_binarynode-v83-win32-x64-unknown —napi_version=7 —node_abi_napi=napi —napi_build_version=0 —node_napi_label=node-v83’ (1)

gyp ERR! find Python checking if «python2» can be used

gyp ERR! find Python — «python2» is not in PATH or produced an error

gyp ERR! find Python checking if «python3» can be used

gyp ERR! find Python — «python3» is not in PATH or produced an error

gyp ERR! find Python checking if the py launcher can be used to find Python 2

gyp ERR! find Python — «py.exe» is not in PATH or produced an error

gyp ERR! find Python checking if Python is C:Python27python.exe

gyp ERR! find Python — «C:Python27python.exe» could not be run

gyp ERR! find Python checking if Python is C:Python37python.exe

gyp ERR! find Python — «C:Python37python.exe» could not be run

gyp ERR! find Python

gyp ERR! find Python **********************************************************

gyp ERR! find Python You need to install the latest version of Python.

gyp ERR! find Python Node-gyp should be able to find and use Python. If not,

gyp ERR! find Python you can try one of the following options:

gyp ERR! find Python — Use the switch —python=»C:PathTopython.exe»

gyp ERR! find Python (accepted by both node-gyp and npm)

gyp ERR! find Python — Set the environment variable PYTHON

gyp ERR! find Python — Set the npm configuration variable python:

gyp ERR! find Python npm config set python «C:PathTopython.exe»

gyp ERR! find Python For more information consult the documentation at:

gyp ERR! find Python https://github.com/nodejs/node-gyp#installation

gyp ERR! find Python **********************************************************

gyp ERR! find Python

gyp ERR! configure error

gyp ERR! stack Error: Could not find any Python installation to use

gyp ERR! stack at PythonFinder.fail (C:Program Filesnodejsnode_modulesnpmnode_modulesnode-gyplibfind-python.js:307:47)

gyp ERR! stack at PythonFinder.runChecks (C:Program Filesnodejsnode_modulesnpmnode_modulesnode-gyplibfind-python.js:136:21)

gyp ERR! stack at PythonFinder.<anonymous> (C:Program Filesnodejsnode_modulesnpmnode_modulesnode-gyplibfind-python.js:225:16)

gyp ERR! stack at PythonFinder.execFileCallback (C:Program Filesnodejsnode_modulesnpmnode_modulesnode-gyplibfind-python.js:271:16)

gyp ERR! stack at exithandler (child_process.js:315:5)

gyp ERR! stack at ChildProcess.errorhandler (child_process.js:327:5)

gyp ERR! stack at ChildProcess.emit (events.js:314:20)

gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)

gyp ERR! stack at onErrorNT (internal/child_process.js:464:16)

gyp ERR! stack at processTicksAndRejections (internal/process/task_queues.js:80:21)

gyp ERR! System Windows_NT 10.0.18363

gyp ERR! command «C:\\\nodejs\node.exe» «C:\\\\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js» «configure» «—fallback-to-build» «—library=static_library» «—module=C:\\\\\grpc\src\node\extension_binary\node-v83-win32-x64-unknown\grpc_node.node» «—module_name=grpc_node» «—module_path=C:\Users\q_osc\empire49\node_modules\grpc\src\node\extension_binary\node-v83-win32-x64-unknown» «—napi_version=7» «—node_abi_napi=napi» «—napi_build_version=0» «—node_napi_label=node-v83»

gyp ERR! cwd C:\node_modulesgrpc

gyp ERR! node -v v14.13.0

gyp ERR! node-gyp -v v5.1.0

gyp ERR! not ok

node-pre-gyp ERR! build error

node-pre-gyp ERR! stack Error: Failed to execute ‘C:Program Filesnodejsnode.exe C:Program Filesnodejsnode_modulesnpmnode_modulesnode-gypbinnode-gyp.js configure —fallback-to-build —library=static_library —module=C:\\grpcsrcnodeextension_binarynode-v83-win32-x64-unknowngrpc_node.node —module_name=grpc_node —module_path=C:\\\\grpcsrcnodeextension_binarynode-v83-win32-x64-unknown —napi_version=7 —node_abi_napi=napi —napi_build_version=0 —node_napi_label=node-v83’ (1)

node-pre-gyp ERR! stack at ChildProcess.<anonymous> (C:\\\\node-pre-gyplibutilcompile.js:83:29)

node-pre-gyp ERR! stack at ChildProcess.emit (events.js:314:20)

node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1047:16)

node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)

node-pre-gyp ERR! System Windows_NT 10.0.18363

node-pre-gyp ERR! command «C:\Program Files\nodejs\node.exe» «C:\\\\grpc\node_modules\node-pre-gyp\bin\node-pre-gyp» «install» «—fallback-to-build» «—library=static_library»

node-pre-gyp ERR! cwd C:\\node_modulesgrpc

node-pre-gyp ERR! node -v v14.13.0

node-pre-gyp ERR! node-pre-gyp -v v0.14.0

node-pre-gyp ERR! not ok

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modulesfsevents):

npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {«os»:»darwin»,»arch»:»any»} (current: {«os»:»win32″,»arch»:»x64″})

npm ERR! code ELIFECYCLE

npm ERR! errno 1

npm ERR! grpc@1.24.2 install: `node-pre-gyp install —fallback-to-build —library=static_library`

npm ERR! Exit status 1

npm ERR!

npm ERR! Failed at the grpc@1.24.2 install 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:

npm ERR! C:\\npm-cache_logs2021-01-03T17_56_25_253Z-debug.log

npm exited with non-zero code: 1

Error: npm exited with non-zero code: 1

at ChildProcess.completionListener (C:\\Roamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:65:13)

at Object.onceWrapper (events.js:421:26)

at ChildProcess.emit (events.js:314:20)

at ChildProcess.cp.emit (C:\\Roamingnpmnode_modulesexpo-clinode_modulescross-spawnlibenoent.js:34:29)

at maybeClose (internal/child_process.js:1047:16)

at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)

…

at Object.spawnAsync [as default] (C:\\Roamingnpmnode_modulesexpo-clinode_modules@expospawn-asyncsrcspawnAsync.ts:26:19)

at NpmPackageManager._runAsync (C:\\Roamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:157:31)

at NpmPackageManager.addAsync (C:\\Roamingnpmnode_modulesexpo-clinode_modules@expopackage-managersrcNodePackageManagers.ts:100:18)

at installAsync (C:\\Roamingnpmnode_modulesexpo-clisrccommandsinstall.ts:129:3)

at Command.<anonymous> (C:\\Roamingnpmnode_modulesexpo-clisrcexp.ts:346:7)

✖ Failed to install expo package with error: npm exited with non-zero code: 1
npm exited with non-zero code: 1
Error: npm exited with non-zero code: 1
    at ChildProcess.completionListener (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:65:13)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
    ...
    at spawnAsync (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
    at NpmPackageManager._runAsync (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:166:31)
    at NpmPackageManager.installAsync (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:82:16)
    at NpmPackageManager.addWithParametersAsync (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:96:18)
    at NpmPackageManager.addAsync (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:109:5)
    at upgradeAsync (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:496:7)
    at actionAsync (/Users/abcd/.nvm/versions/node/v16.18.0/lib/node_modules/expo-cli/src/commands/info/upgradeAsync.ts:42:3)

1 ответ