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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_getAbsolutePath(), which is used for loading the app binary, always assumes that the app is located in the current working directory. With react-native, this assumption is no longer true because of the now commonplace use of expo, which puts the binary down in ~/.expo. This isn't an issue with one programmer on a team, since they can type "../../../.expo" etc., but when sharing code between two programmers who have different file system structures, it becomes problematic.
The text was updated successfully, but these errors were encountered:
I was surprised too. But then again, this single Expo install gets shared by all Expo-enabled React apps, so it would make even less sense to put them in individual project folders.
There is no mention of configuration on this point in their docs...
In Device.js:
_getAbsolutePath()
, which is used for loading the app binary, always assumes that the app is located in the current working directory. With react-native, this assumption is no longer true because of the now commonplace use of expo, which puts the binary down in~/.expo
. This isn't an issue with one programmer on a team, since they can type "../../../.expo" etc., but when sharing code between two programmers who have different file system structures, it becomes problematic.The text was updated successfully, but these errors were encountered: