Hi, The whole actions in the command prompt is added below for getting the exact problem .
Hope an earliest solution, please
Microsoft Windows [Version 10.0.17763.437]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\Admin>npm install expo-cli --global
npm WARN deprecated 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).npm WARN deprecated 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).npm WARN deprecated 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).npm WARN deprecated 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).npm WARN deprecated 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.
npm WARN deprecated 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.
C:\Users\Admin\AppData\Roaming\npm\expo → C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\bin\expo.js
C:\Users\Admin\AppData\Roaming\npm\expo-cli → C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\bin\expo.js
npm WARN ts-pnp@1.1.2 requires a peer of typescript@* but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-darwin-ia32@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-darwin-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-darwin-ia32@2.2.8: wanted {“os”:“darwin”,“arch”:“ia32”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-darwin-x64@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-darwin-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-darwin-x64@2.2.8: wanted {“os”:“darwin”,“arch”:“x64”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-freebsd-ia32@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-freebsd-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-freebsd-ia32@2.2.8: wanted {“os”:“freebsd”,“arch”:“ia32”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-freebsd-x64@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-freebsd-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-freebsd-x64@2.2.8: wanted {“os”:“freebsd”,“arch”:“x64”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-arm@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-linux-arm):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-arm@2.2.8: wanted {“os”:“linux”,“arch”:“arm”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-arm64@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-linux-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-arm64@2.2.8: wanted {“os”:“linux”,“arch”:“arm64”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-ia32@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-linux-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-ia32@2.2.8: wanted {“os”:“linux”,“arch”:“ia32”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-linux-x64@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-linux-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-linux-x64@2.2.8: wanted {“os”:“linux”,“arch”:“x64”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-sunos-x64@2.2.8 (node_modules\expo-cli\node_modules@expo\ngrok-bin-sunos-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-sunos-x64@2.2.8: wanted {“os”:“sunos”,“arch”:“x64”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/ngrok-bin-win32-ia32@2.2.8-beta.1 (node_modules\expo-cli\node_modules@expo\ngrok-bin-win32-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/ngrok-bin-win32-ia32@2.2.8-beta.1: wanted {“os”:“win32”,“arch”:“ia32”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @expo/traveling-fastlane-darwin@1.9.3 (node_modules\expo-cli\node_modules@expo\traveling-fastlane-darwin):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for @expo/traveling-fastlane-darwin@1.9.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\expo-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
- expo-cli@2.16.1
updated 2 packages in 103.367s
C:\Users\Admin>cd C:\Users\Admin\Desktop\wilcity-app\wilcity-app
C:\Users\Admin\Desktop\wilcity-app\wilcity-app>npm install
grpc@1.20.0 install C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc
node-pre-gyp install --fallback-to-build --library=static_library
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): …node-precompiled-binaries.grpc.io/grpc/v1.20.0/node-v72-win32-x64-unknown.tar.gz
node-pre-gyp WARN Pre-built binaries not found for grpc@1.20.0 and node@12.1.0 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe ENOENT
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:19)
gyp ERR! stack at onErrorNT (internal/child_process.js:431:16)
gyp ERR! stack at processTicksAndRejections (internal/process/task_queues.js:84:17)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js” “build” “–fallback-to-build” “–library=static_library” “–module=C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\src\node\extension_binary\node-v72-win32-x64-unknown\grpc_node.node” “–module_name=grpc_node” “–module_path=C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\src\node\extension_binary\node-v72-win32-x64-unknown” “–napi_version=4” “–node_abi_napi=napi” “–napi_build_version=0” “–node_napi_label=node-v72”
gyp ERR! cwd C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc
gyp ERR! node -v v12.1.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in node-gyp.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR! <…github.com/nodejs/node-gyp/issues>
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute ‘C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --library=static_library --module=C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\src\node\extension_binary\node-v72-win32-x64-unknown\grpc_node.node --module_name=grpc_node --module_path=C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\src\node\extension_binary\node-v72-win32-x64-unknown --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72’ (7)
node-pre-gyp ERR! stack at ChildProcess. (C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:196:13)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1000:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:267:5)
node-pre-gyp ERR! System Windows_NT 10.0.17763
node-pre-gyp ERR! command “C:\Program Files\nodejs\node.exe” “C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\node_modules\node-pre-gyp\bin\node-pre-gyp” “install” “–fallback-to-build” “–library=static_library”
node-pre-gyp ERR! cwd C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc
node-pre-gyp ERR! node -v v12.1.0
node-pre-gyp ERR! node-pre-gyp -v v0.12.0
node-pre-gyp ERR! not ok
Failed to execute ‘C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --library=static_library --module=C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\src\node\extension_binary\node-v72-win32-x64-unknown\grpc_node.node --module_name=grpc_node --module_path=C:\Users\Admin\Desktop\wilcity-app\wilcity-app\node_modules\grpc\src\node\extension_binary\node-v72-win32-x64-unknown --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72’ (7)
npm WARN eslint-plugin-react-native@3.7.0 requires a peer of eslint@^3.17.0 || ^4 || ^5 but none is installed. You must install peer dependencies yourself.
npm WARN expo-asset@1.1.1 requires a peer of expo-file-system@~1.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN expo-core@1.2.0 requires a peer of expo-react-native-adapter@~1.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN expo-camera@1.1.1 requires a peer of react@^16.4.0 but none is installed. You must install peer dependencies yourself.
npm WARN expo-gl@1.0.2 requires a peer of react@^16.4.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-native-maps@0.21.0 requires a peer of react-native@^0.51 || ^0.52 || ^0.53 || ^0.54 but none is installed. You must install peer dependencies yourself.
npm WARN react-native-reanimated@1.0.0-alpha.6 requires a peer of react@16.0.0-alpha.6 but none is installed. You must install peer dependencies yourself.
npm WARN react-native-reanimated@1.0.0-alpha.6 requires a peer of react-native@^0.44.1 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! grpc@1.20.0 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.20.0 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:\Users\Admin\AppData\Roaming\npm-cache_logs\2019-05-04T08_09_36_827Z-debug.log
C:\Users\Admin\Desktop\wilcity-app\wilcity-app>exp build:android
‘exp’ is not recognized as an internal or external command,
operable program or batch file.
An Expo user account is required to proceed.
? How would you like to authenticate? Log in with an existing Expo account
? Username/Email Address: mochashi
? Password: [hidden]
Success. You are now logged in as mochashi.
Splash resizeMode is set to ‘cover’, but you haven’t provided any images for different DPIs.
Be aware that your splash image will be used as xxxhdpi asset and its actual size will be different depending on device’s DPI.
See …docs.expo.io/versions/latest/guides/splash-screens/#differences-between-environments—android for more information
Checking if there is a build in progress…
? Would you like to upload a keystore or have us generate one for you?
If you don’t know what this means, let us handle it! 
false
Unable to find an existing Expo CLI instance for this directory, starting a new one…
Starting Metro Bundler on port 19001.
Metro Bundler ready.
Tunnel ready.
Publishing to channel ‘default’…
Building iOS bundle
Unable to resolve module firebase from C:\Users\Admin\Desktop\wilcity-app\wilcity-app\app\actions\actionMessage.js: Module firebase does not exist in the Haste module map
This might be related to …github.com/facebook/react-native/issues/4968
To resolve try the following:
- Clear watchman watches:
watchman watch-del-all. - Delete the
node_modulesfolder:rm -rf node_modules && npm install. - Reset Metro Bundler cache:
rm -rf /tmp/metro-bundler-cache-*ornpm start -- --reset-cache. 4. Remove haste cache:rm -rf /tmp/haste-map-react-native-packager-*.
Unable to resolve “firebase” from “app\actions\actionMessage.js”
Failed building JavaScript bundle.
Cannot read property ‘status’ of undefined
Set EXPO_DEBUG=true in your env to view the stack trace.
Building JavaScript bundle [======================== ] 53%
C:\Users\Admin\Desktop\wilcity-app\wilcity-app>true
‘true’ is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Admin\Desktop\wilcity-app\wilcity-app>
C:\Users\Admin\Desktop\wilcity-app\wilcity-app>expo build:android
Splash resizeMode is set to ‘cover’, but you haven’t provided any images for different DPIs.
Be aware that your splash image will be used as xxxhdpi asset and its actual size will be different depending on device’s DPI.
See …docs.expo.io/versions/latest/guides/splash-screens/#differences-between-environments—android for more information
Checking if there is a build in progress…
? Would you like to upload a keystore or have us generate one for you?
If you don’t know what this means, let us handle it!
false
Unable to find an existing Expo CLI instance for this directory, starting a new one…
Starting Metro Bundler on port 19001.
Metro Bundler ready.
Tunnel ready.
Publishing to channel ‘default’…
Building iOS bundle
Unable to resolve module firebase from C:\Users\Admin\Desktop\wilcity-app\wilcity-app\app\actions\actionMessage.js: Module firebase does not exist in the Haste module map
This might be related to …github.com/facebook/react-native/issues/4968
To resolve try the following:
- Clear watchman watches:
watchman watch-del-all. - Delete the
node_modulesfolder:rm -rf node_modules && npm install. - Reset Metro Bundler cache:
rm -rf /tmp/metro-bundler-cache-*ornpm start -- --reset-cache. 4. Remove haste cache:rm -rf /tmp/haste-map-react-native-packager-*.
Unable to resolve “firebase” from “app\actions\actionMessage.js”
Failed building JavaScript bundle.
Cannot read property ‘status’ of undefined
Set EXPO_DEBUG=true in your env to view the stack trace.
Building JavaScript bundle [======================== ] 53%
C:\Users\Admin\Desktop\wilcity-app\wilcity-app>