EAS build error when reaching "install dependencies" - firebase

I've started using react native with expo not long ago so I am a bit lost.
When trying to build the application with the command:
eas build --profile development --platform android
The build fails when it reaches the install dependencies part
Running "npm install" in the root dir of your repository 2[stderr] npm ERR! code ERESOLVE3[stderr] npm ERR!4[stderr] ERESOLVE could not resolve5[stderr] npm ERR! 6[stderr] npm ERR!7[stderr] While resolving: #react-native-firebase/auth#16.2.08[stderr] npm ERR! Found: #react-native-firebase/app#15.4.09[stderr] npm ERR! node_modules/#react-native-firebase/app10[stderr] npm ERR! #react-native-firebase/app#"~15.4.0" from the root project11[stderr] npm ERR! 12[stderr] npm ERR! Could not resolve dependency:13[stderr] npm ERR! peer #react-native-firebase/app#"16.2.0" from #react-native-firebase/auth#16.2.014[stderr] npm ERR! node_modules/#react-native-firebase/auth15[stderr] npm ERR! #react-native-firebase/auth#"^16.2.0" from the root project16[stderr] npm17[stderr] ERR! 18[stderr] npm ERR! Conflicting peer dependency: #react-native-firebase/app#16.2.019[stderr] npm ERR! node_modules/#react-native-firebase/app20[stderr] npm ERR! peer #react-native-firebase/app#"16.2.0" from #react-native-firebase/auth#16.2.021[stderr] npm ERR! node_modules/#react-native-firebase/auth22[stderr] npm ERR! #react-native-firebase/auth#"^16.2.0" from the root project23[stderr] npm ERR! 24[stderr] npm ERR! Fix the upstream dependency conflict, or retry25[stderr] npm ERR! this command with --force, or --legacy-peer-deps26[stderr] npm ERR! to accept an incorrect (and potentially broken) dependency resolution.27[stderr] npm ERR! 28[stderr] npm ERR! See /home/expo/.npm/eresolve-report.txt for a full report.29[stderr] 30[stderr] npm ERR! A complete log of this run can be found in:31[stderr] npm ERR! /home/expo/.npm/_logs/2022-11-26T18_50_07_398Z-debug-0.log32npm exited with non-zero code: 1
I have tried clearing the cache and rebuilding the app. When I try npx expo start --dev-client the app works fine.
This is my package.json:
{
"name": "wallet",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web"
},
"dependencies": {
"#react-native-firebase/app": "~15.4.0",
"#react-native-firebase/auth": "^16.2.0",
"#react-native-google-signin/google-signin": "^8.0.1",
"#react-navigation/bottom-tabs": "^6.4.0",
"#react-navigation/drawer": "^6.5.0",
"#react-navigation/material-top-tabs": "^6.3.0",
"#react-navigation/native": "^6.0.13",
"#react-navigation/native-stack": "^6.9.1",
"#rneui/base": "^4.0.0-rc.7",
"#rneui/themed": "^4.0.0-rc.7",
"expo": "~46.0.16",
"expo-dev-client": "~1.3.1",
"expo-font": "~10.2.0",
"expo-linear-gradient": "~11.4.0",
"expo-local-authentication": "~12.3.0",
"expo-status-bar": "~1.4.0",
"formik": "^2.2.9",
"moment": "^2.29.4",
"react": "18.0.0",
"react-native": "0.69.6",
"react-native-gesture-handler": "~2.5.0",
"react-native-icon-badge": "^1.1.3",
"react-native-linear-gradient": "^2.6.2",
"react-native-pager-view": "^5.4.24",
"react-native-reanimated": "~2.9.1",
"react-native-recaptcha-that-works": "^1.3.2",
"react-native-safe-area-context": "^4.3.1",
"react-native-screens": "~3.15.0",
"react-native-tab-view": "^3.3.0",
"react-native-webview": "11.23.0",
"styled-components": "^5.3.6"
},
"devDependencies": {
"#babel/core": "^7.12.9"
},
"private": true
}

I come a cross the same issue today while building for production. I solved with installing dependencies by:
yarn install
After that eas switced to yarn instead of using npm to install the packages. Hope its works for you.

After digging into the specific missing or conflicting dependencies, I managed to fix the issue by:
deleting node_modules (from terminal) with rm -rf node_modules.
update react to version 18.1.0
Install react-dom 18.1.0
After all that, I managed to build the app with EAS, but after I launched it, it instantly crashed with no errors on my device.
after debugging my device errors by connecting it to my PC,
I saw that some of my expo dependencies are not updated, so I used the following:
expo doctor --fix dependencies.
After that, the app was finally. launching correctly
Thank you, #Kaosc, for leading me to this fix.
Some of the things above might not be connected, but that's what I did.

I did this in my terminal in the root of my project:
expo doctor
It gave me this:
Expected package #expo/config-plugins#^5.0.2
Found invalid:
#expo/config-plugins#4.0.6
(for more info, run: npm why #expo/config-plugins)
Some dependencies are incompatible with the installed expo package version:
- expo-status-bar - expected version: ~1.4.2 - actual version installed: 1.2.0
- expo-updates - expected version: ~0.15.6 - actual version installed: 0.11.7
- react - expected version: 18.1.0 - actual version installed: 18.2.0
- react-dom - expected version: 18.1.0 - actual version installed: 17.0.1
- react-native - expected version: 0.70.5 - actual version installed: 0.70.6
- react-native-reanimated - expected version: ~2.12.0 - actual version installed: 2.13.0
- react-native-safe-area-context - expected version: 4.4.1 - actual version installed: 3.3.2
- react-native-screens - expected version: ~3.18.0 - actual version installed: 3.10.2
- react-native-web - expected version: ~0.18.9 - actual version installed: 0.17.1
- react-native-webview - expected version: 11.23.1 - actual version installed: 11.15.0
Your project may not work correctly until you install the correct versions of the packages.
To install the correct versions of these packages, please run: expo doctor --fix-dependencies,
or install individual packages by running expo install [package-name ...]
Then I did this:
expo doctor --fix-dependencies
Then I go this and no more errors:
Expected package #expo/config-plugins#^5.0.2
Found invalid:
#expo/config-plugins#4.0.6
(for more info, run: npm why #expo/config-plugins)
Some dependencies are incompatible with the installed expo package version:
- expo-status-bar - expected version: ~1.4.2 - actual version installed: 1.2.0
- expo-updates - expected version: ~0.15.6 - actual version installed: 0.11.7
- react - expected version: 18.1.0 - actual version installed: 18.2.0
- react-dom - expected version: 18.1.0 - actual version installed: 17.0.1
- react-native - expected version: 0.70.5 - actual version installed: 0.70.6
- react-native-reanimated - expected version: ~2.12.0 - actual version installed: 2.13.0
- react-native-safe-area-context - expected version: 4.4.1 - actual version installed: 3.3.2
- react-native-screens - expected version: ~3.18.0 - actual version installed: 3.10.2
- react-native-web - expected version: ~0.18.9 - actual version installed: 0.17.1
- react-native-webview - expected version: 11.23.1 - actual version installed: 11.15.0
This command is being executed with the global Expo CLI. Learn more: https://blog.expo.dev/the-new-expo-cli-f4250d8e3421
To use the local CLI instead (recommended in SDK 46 and higher), run:
› npx expo install
Installing 10 SDK 47.0.0 compatible native modules using npm.
> npm install
added 10 packages, removed 97 packages, changed 33 packages, and audited 1216 packages in 2m
57 packages are looking for funding
run `npm fund` for details
7 vulnerabilities (1 low, 5 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.

Delete package-lock.json and try again

Related

Connecting Firebase to an React Native App that's using Expo

I am currently trying to connect Firebase to my React Native app that uses Expo. Im currently using this guide: https://docs.expo.io/guides/using-firebase/?fbclid=IwAR0c7g8a-005utr_ROomb_k3ptlAHel3kq004AtFbNkV9iWREeapzR0Dabg and it lead me to the github "Firebase JS SDK". I downloaded the whole github repo (https://github.com/firebase/firebase-js-sdk) and like tried following the instructions on the github such as downloading node, yarn, and java but I am confused on what to do next with the downloaded repo. I have tried running the command "npm install" to try and install the dependencies but I get this error:
npm WARN deprecated tslint#6.1.2: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request#2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated core-js#2.6.11: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated chokidar#2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated mkdirp-promise#5.0.1: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! Unexpected end of JSON input while parsing near '...cMP/3jKIr36/huSPHVVgD'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Ban-Jian\AppData\Roaming\npm-cache\_logs\2020-05-19T23_15_25_175Z-debug.log
And when I run the command: "yarn build" I get this error:
lerna ERR! yarn run build exited 2 in '#firebase/firestore'
lerna ERR! yarn run build stdout:
$ tsc -m es2015 --moduleResolution node scripts/*.ts
error TS6053: File 'scripts/*.ts' not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run build stderr:
error Command failed with exit code 2.
lerna ERR! yarn run build exited 2 in '#firebase/firestore'
lerna WARN complete Waiting for 4 child processes to exit. CTRL-C to exit immediately.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I guess my question is: How do I properly set up the SDK I downloaded from the github?

npm ERR! peer dep missing: firebase-admin#^7.0.0, required by firebase-functions#2.3.1

I am trying to understand how to get the version of firebase-admin that is required. My scenario is this:
MYPATH\functions>npm list firebase-admin
functions# MYPATH\functions
`-- UNMET PEER DEPENDENCY firebase-admin#6.5.1
npm ERR! peer dep missing: firebase-admin#^7.0.0, required by firebase-functions#2.3.1
Running npm update firebase-admin does not change anything.
package.json contains this line:
"dependencies": {
...
"firebase-admin": "^6.5.1",
What am I supposed to do?
UPDATE:
When doing firebase serve I get this error:
! Your requested "node" version "6" doesn't match your global version "10"
....
+ hosting: Local server: http://localhost:5000
! The Cloud Functions emulator requires the module "firebase-admin" to be installed. This package is in your package.json, but it's not available. You probably need to run "npm install" in your functions directory.
i functions: Your functions could not be parsed due to an issue with your node_modules (see above)
'npm update' is working, however the '^' carat against "firebase-admin" in your package.json will limit the updates to the 6.x releases - so it's not getting anything newer then the 6.5.1 release.
You can manually change the version of "firebase-admin" in your package.json to "^7.0.0" and then run 'npm install'. This will grab the latest release in the 7.x.x range.

error updating to meteor 1.3.4.4

Meteor instructed to do meteor update from 1.3.4.3 to update to 1.3.4.4 and after I did that, I got the following errors.
Not sure what to do at this point, any idea? Thanks
$meteor update
=> Errors
while initializing project:
While loading package fourseven: scss# 3.3.3_3:
error: Command failed:
module.js: 340
throw err; ^
Error: Cannot find module '../'
at Function.Module._resolveFilename(module.js: 338: 15)
at Function.Module._load(module.js: 280: 25)
at Module.require(module.js: 364: 17)
at require(module.js: 380: 17)
at Object. < anonymous >
(/Users/empl1 / .meteor / packages / fourseven_scss / .3.3.3_3.ecnkm4++os.osx.x86_64 + web.browser + web.cordova / plugin.compileScssBatch.os.osx.x86_64 / npm / node_modules / meteor / compileScssBatch / compileScssBatch / node_modules / .temp - 1dptekz / node_modules / node - sass / node_modules / cross - spawn / node_modules / spawn - sync / node_modules /
try -thread - sleep / node_modules / thread - sleep / node_modules / .bin / node - pre - gyp: 15: 20)
at Module._compile(module.js: 456: 26)
at Object.Module._extensions..js(module.js: 474: 10)
at Module.load(module.js: 356: 32)
at Function.Module._load(module.js: 312: 12)
at Function.Module.runMain(module.js: 497: 10)
npm ERR!Darwin 15.5.0
npm ERR!argv "node"
"/Users/empl1/.meteor/packages/meteor-tool/.1.3.5_1.hzx8lp++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/npm"
"rebuild"
"--no-bin-links"
"--update-binary"
npm ERR!node v0.10.46
npm ERR!npm v3.10.5
npm ERR!code ELIFECYCLE
npm ERR!thread - sleep# 1.0.4 install: `node-pre-gyp install
--fallback-to-build`
npm ERR!Exit status 8
npm ERR!
npm ERR!Failed at the thread - sleep# 1.0.4 install script 'node-pre-gyp
install --fallback-to-build'.
npm ERR!Make sure you have the latest version of node.js and npm
installed.
npm ERR!If you do,
this is most likely a problem with the
thread - sleep package,
npm ERR!not with npm itself.
npm ERR!Tell the author that this fails on your system:
npm ERR!node - pre - gyp install--fallback - to - build
npm ERR!You can get information on how to open an issue
for this
project with:
npm ERR!npm bugs thread - sleep
npm ERR!Or
if that isn 't available, you can get their info via:
npm ERR! npm owner ls thread-sleep
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!
/Users/empl1/.meteor/packages/fourseven_scss/.3.3.3_3.ecnkm4++os.osx.x86_64+web.browser+web.cordova/plugin.compileScssBatch.os.osx.x86_64/npm/node_modules/meteor/compileScssBatch/compileScssBatch/node_modules/.temp-1dptekz/npm-debug.log
module.js:340
throw err;
^
Error: Cannot find module '.. / '
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous>
(/Users/empl1/.meteor/packages/fourseven_scss/.3.3.3_3.ecnkm4++os.osx.x86_64+web.browser+web.cordova/plugin.compileScssBatch.os.osx.x86_64/npm/node_modules/meteor/compileScssBatch/compileScssBatch/node_modules/.temp-1dptekz/node_modules/node-sass/node_modules/cross-spawn/node_modules/spawn-sync/node_modules/try-thread-sleep/node_modules/thread-sleep/node_modules/.bin/node-pre-gyp:15:20)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
npm ERR! Darwin 15.5.0
npm ERR! argv "node"
"/Users/empl1/.meteor/packages/meteor-tool/.1.3.5_1.hzx8lp++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/npm"
"rebuild" "--no-bin-links" "--update-binary"
npm ERR! node v0.10.46
npm ERR! npm v3.10.5
npm ERR! code ELIFECYCLE
npm ERR! thread-sleep#1.0.4 install: `node-pre-gyp install
--fallback-to-build`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the thread-sleep#1.0.4 install script '
node - pre - gyp
install--fallback - to - build '.
npm ERR! Make sure you have the latest version of node.js and npm
installed.
npm ERR! If you do, this is most likely a problem with the
thread-sleep package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this
project with:
npm ERR! npm bugs thread-sleep
npm ERR! Or if that isn'
t available, you can get their info via:
npm ERR!npm owner ls thread - sleep
npm ERR!There is likely additional logging output above.
npm ERR!Please include the following file with any support request:
npm ERR!
/Users/empl1 / .meteor / packages / fourseven_scss / .3.3.3_3.ecnkm4++os.osx.x86_64 + web.browser + web.cordova / plugin.compileScssBatch.os.osx.x86_64 / npm / node_modules / meteor / compileScssBatch / compileScssBatch / node_modules / .temp - 1dptekz / npm - debug.log
This might be related to a magration from a lesser version of Meteor 1.2 to a 1.3+.
Warnings are related to this package:meteor-scss
On its documentation it recommends to do the following for 1.3+ versions.
meteor remove standard-minifier-css
meteor add seba:minifiers-autoprefixer
If that does'nt work it also talks about locking a version for specific Meteor Versions
Note: Due to same changes between Meteor 1.3.0-1.3.1 and Meteor 1.3.2+, Users of Meteor 1.3.0 or 1.3.1 are advised to use version 3.4.2 of fourseven:scss
You can do this inside ./meteor/versions folder.

FlowRouter no longer working after Meteor + React deployment using Mupx

I have a Meteor + React app that works fine locally. I've tested using the --production flag and there are no issues.
Once I use mupx to deploy to my server, the deployment is successful but when I go to the deployed app it throws "There is no route for the path: /".
My routes.js file is located in the client directory.
Here is my mupx logs -f result
npm WARN deprecated This version of npm lacks support for important
features, npm WARN deprecated such as scoped packages, offered by the
primary npm npm WARN deprecated registry. Consider upgrading to at
least npm#2, if not the npm WARN deprecated latest stable version. To
upgrade to npm#2, run: npm WARN deprecated npm WARN deprecated npm -g
install npm#latest-2 npm WARN deprecated npm WARN deprecated To
upgrade to the latest stable version, run: npm WARN deprecated npm
WARN deprecated npm -g install npm#latest npm WARN deprecated npm
WARN deprecated (Depending on how Node.js was installed on your
system, you npm WARN deprecated may need to prefix the preceding
commands with sudo, or if npm WARN deprecated on Windows, run them
from an Administrator prompt.) npm WARN deprecated npm WARN
deprecated If you're running the version of npm bundled with npm WARN
deprecated Node.js 0.10 LTS, be aware that the next version of 0.10
LTS npm WARN deprecated will be bundled with a version of npm#2, which
has some small npm WARN deprecated backwards-incompatible changes made
to npm run-script and npm WARN deprecated semver behavior. npm WARN
package.json meteor-dev-bundle#0.0.0 No description npm WARN
package.json meteor-dev-bundle#0.0.0 No repository field. npm WARN
package.json meteor-dev-bundle#0.0.0 No README data
fibers#1.0.8 install
/bundle/bundle/programs/server/node_modules/fibers node build.js ||
nodejs build.js make: Entering directory
/bundle/bundle/programs/server/node_modules/fibers/build' CXX(target)
Release/obj.target/fibers/src/fibers.o CXX(target)
Release/obj.target/fibers/src/coroutine.o CC(target)
Release/obj.target/fibers/src/libcoro/coro.o SOLINK_MODULE(target)
Release/obj.target/fibers.node SOLINK_MODULE(target)
Release/obj.target/fibers.node: Finished COPY Release/fibers.node
make: Leaving
directory/bundle/bundle/programs/server/node_modules/fibers/build'
Installed in
/bundle/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node
npm WARN cannot run in wd meteor-dev-bundle#0.0.0 node npm-rebuild.js
(wd=/bundle/bundle/programs/server) ansi-regex#0.2.1
node_modules/ansi-regex
ansi-styles#1.1.0 node_modules/ansi-styles
escape-string-regexp#1.0.5 node_modules/escape-string-regexp
chalk#0.5.1 node_modules/chalk
has-ansi#0.1.0 node_modules/has-ansi
strip-ansi#0.3.0 node_modules/strip-ansi
supports-color#0.2.0 node_modules/supports-color
eachline#2.3.3 node_modules/eachline
type-of#2.0.1 node_modules/type-of
amdefine#1.0.0 node_modules/amdefine
asap#2.0.3 node_modules/asap
underscore#1.5.2 node_modules/underscore
meteor-promise#0.5.1 node_modules/meteor-promise
promise#7.0.4 node_modules/promise
source-map-support#0.3.2 node_modules/source-map-support
semver#4.1.0 node_modules/semver
source-map#0.1.32 node_modules/source-map
fibers#1.0.8 node_modules/fibers
=> Starting meteor app on port:80

Can not upgrade nuclide package to 0.125.0 on atom

Info
$ apm -v
apm 1.6.0
npm 2.13.3
node 0.10.40
python 2.7.10
git 2.6.4
$ apm update
Package Updates Available (1)
└── nuclide 0.124.0 -> 0.125.0
Would you like to install these updates? (yes)
Error:
npm WARN engine nuclide#0.125.0: wanted: {"atom":">=1.5.3","node":">=4.1.1"} (current: {"node":"0.10.40","npm":"2.13.3"})
npm ERR! Darwin 15.4.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/chandan/.atom/.apm/.apmrc" "--userconfig" "/Users/chandan/.atom/.apmrc" "install" "/private/var/folders/jx/80gvpbb525z56t19l_n172hw0000gn/T/d-116223-40264-1wsir87/package.tgz" "--target=0.34.5" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm v2.13.3
npm ERR! version not found: relative-date#1.1.2
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /private/var/folders/jx/80gvpbb525z56t19l_n172hw0000gn/T/apm-install-dir-116223-40264-17hzbk1/npm-debug.log
Please let me know if i am doing something wrong or if there is a workaround on how to upgrade this nuclide package.
For now I built nuclide manually according to this guide: http://nuclide.io/docs/advanced-topics/building-from-source.
git clone https://github.com/facebook/nuclide.git
cd nuclide
npm install
apm link
It has solved the problem for me.
This is resolved.
This error occurred during the infamous 'left-pad' unpublishing of March 2016. 'left-pad' received the most mentions, but 'relative-date' was among the packages that were unpublished as well.
This was not a problem in Nuclide itself but rather in the downloading of its dependencies.

Resources