expo-cli | deploying universal Expo and React Native apps | Frontend Framework library

New to development, trying to get my development environment setup - any ideas as to how to fix this issue?

Command Entered: npm install -g expo-cli

Error, see below:

After migrating from expo-cli to eas-cli, I make the app build by using command eas build -p android.

Then, in order to be able to use it within my custom CI, I get the app archive download url. I used to use expo url:apk. This command is not working anymore, since I make the build with eas.

Does anyone know how to get the download url using eas?

I am getting this issue in react native. The things were working fine until I decicded to rerun the project doing yarn install

Here is complete error

TypeError: undefined is not an object (evaluating '_expoModulesCore.NativeModulesProxy.ExpoSplashScreen') at node_modules\react-native\Libraries\LogBox\LogBox.js:148:8 in registerError at node_modules\react-native\Libraries\LogBox\LogBox.js:59:8 in errorImpl at node_modules\react-native\Libraries\LogBox\LogBox.js:33:4 in console.error at node_modules\expo\build\environment\react-native-logs.fx.js:27:4 in error at node_modules\react-native\Libraries\Core\ExceptionsManager.js:104:6 in reportException at node_modules\react-native\Libraries\Core\ExceptionsManager.js:171:19 in handleException at node_modules\react-native\Libraries\Core\setUpErrorHandling.js:24:6 in handleError at node_modules\expo-error-recovery\build\ErrorRecovery.fx.js:12:21 in ErrorUtils.setGlobalHandler$argument_0 at node_modules\regenerator-runtime\runtime.js:63:36 in tryCatch at node_modules\regenerator-runtime\runtime.js:294:29 in invoke at node_modules\regenerator-runtime\runtime.js:63:36 in tryCatch at node_modules\regenerator-runtime\runtime.js:155:27 in invoke at node_modules\regenerator-runtime\runtime.js:165:18 in PromiseImpl.resolve.then$argument_0 at node_modules\react-native\node_modules\promise\setimmediate\core.js:37:13 in tryCallOne at node_modules\react-native\node_modules\promise\setimmediate\core.js:123:24 in setImmediate$argument_0 at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:130:14 in _callTimer at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:181:14 in _callImmediatesPass at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:441:30 in callImmediates at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:387:6 in __callImmediates at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:135:6 in __guard$argument_0 at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:364:10 in __guard at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:134:4 in flushedQueue

I have tried with update expo-cli, expo-splash-screen and with cache clear command expo r -c

Let me know if there is anyone who can help.

Unfortunately, we have projects with different nodejs versions. I am not sure if this is like java where I can have multiple jdks installed(multiple nodejs installed) and each project magically uses the correct version via a config file? Also, most commands in tutorials are not including version numbers when installing tools and libraries like so

• npm install -g expo-cli (tool)
• npm install @react-navigation/native (library)

Coming from gradle with the gradle wrapper where everyone on the team uses the tools and library versions defined in the build.gradle file, this is odd to me. In the gradle world, everyone on the team uses the same exact version of gradle(gradle itself ensures if one person upgrades it in the repo, everyone gets the upgrade and stays in sync on the same version). Then there is plugins/tools and those versions are defined and then libraries and those versions are defined.

• How do I guarantee everyone is using the same npm, node, expo, etc. tools?
• How do I guarantee everyone is using the same libraries?
• How do I guarantee everyone is using the same typescript?

Ideally, we upgrade any of these in the repo + any fixes to the upgrade so on checkout, developers start using the new tool + new *.tsx files so it is seamless much like in the gradle world. In gradle, I upgrade the

• version via a property
• versions of plugins/tools
• build.gradle files
• any source code files

and check that all in as a unit such that any developer that checks out is using all the correct versions together. I want this in react-native for our ios/android mobile project or as close as I can get.

I have hacked things before as in installing 'ant' into the git repo and this worked wonders(even though it is such an ugly hack) and everyone used the tool in the repo instead of the one on their OS. Perhaps there is a way to do that?

A bloated repo with binaries was worth it's weight in gold to prevent version compatibility hell as people upgraded libraries over time. NOT only that we found that tool bugs were easier to track down as we could revert the repo. NOT only that, we could reproduce builds form 1 year ago as the tooling was reverted where todays npm tools can't build the 1 year ago thing due to all the changes. The advantages just kept piling up and up and I can't even remember all of them.

Tooling running from the repo either via bootstrap like gradle wrapper or full blown thing is generally the best option until the full blown thing is really bloated but even then locking it to a hash on another tool repo could be better

Any ideas welcome here to put my team on all the same tooling(works great for people joining the company or team from another project as well to not have to install much).

thanks, Dean

I have been using this setup for almost half a year now and I upgraded the Expo SDK to 44 (erased all content and settings on the simulator). Ever since, the expo client won't install on the simulator.

Things I have tried:

• run expo client:install:ios
• uninstall and reinstall expo
• uninstall and reinstall watchman
• tried different simulators (15.0 that I used so far)
• creating a new blank expo project
• open the simulator first and then npm start
• I even did a complete MacBook reset (factory, needed to wipe anyway) and reinstalled following the expo documentation.

I read something about installing expo without sudo, but then it will throw errors and will simply not install.

New blank expo project infos:

Expo : 44.0.0 expo-cli: 5.0.3 react-native: 0.64.3

Hope someone knows the solution to this, I really want to get back programming.

I have an iOS Expo based project using the managed workflow. My app runs perfectly fine on the simulator and on Expo Go but on my device (installed with TestFlight) it crashes immediately after seeing the splash screen fade away for a second. Can anyone detect the problem is based on the below logs?

Expo Diagnostics:

I have recently upgraded my app from SDK 40 to SDK 44 and came across this error App.js: [BABEL]: Unexpected token '.' (While processing: /Users/user/path/to/project/node_modules/babel-preset-expo/index.js)

Error Stack Trace:

I'm trying to include a link to an external url with key/value pairs prefaced with & using react-native-render-html in an app developed with expo but when I run the code on Expo Go client I've got the error:

TypeError: undefined is not an object (evaluating 'this.entityTrie[0]')

I'm using:

• expo v. 43.0.2
• expo-cli v. 4.12.11
• Expo Go v. 2.22.3
• react-native-render-html v.6.3.1

I'm running expo-cli on Windows 10 Pro and I've tested the bundle on 2 different devices: one Redmi Note 7 with Android 9 and one Redmi 9C with Android 10.

The most disconcerting thing is that if I generate the .apk with expo and install it on the devices it works.

The code is quite simple:

When I install expo it installs but it doesn't install. Here are the details about the issue.

I start off by typing: