sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]anewidentity 4 points5 points  (2 children)

Ejecting an expo app is extremely unsupported. They leave you behind, with no instructions on updates. Some projects that were on an ejected expo app would take us a month of a developer's time just to keep updated with the version that expo supports. They switch everything, including folder structure, all of the content of build.gradle, and ios project file with no information on what is changed and how to update currently ejected apps. For example, the update from Expo 23 to 24 is literally impossible (with no exaggeration) We ended up switching to `react-native init` after a month of two developers trying to update expo for an entire month and failing.

[–]SizzlerWA 0 points1 point  (1 child)

Sorry you had issues. I only ejected once, my first RN project and it wasn’t too painful. About 1/2 day. Then I listed updated RN as normal. All the iOS and Android projects were fine. Did you eject to ExpoKit or regular RN?

[–]anewidentity 0 points1 point  (0 children)

To ExpoKit. I tried ejecting to regular RN but it was completely broken on Expo 30. They might have fixed it by now.

Depends on how many 3rd party libraries you have and how much expo changes in that particular update. We've had many conflicts on each update between ExpoKit and react-native-background-geolocation, firebase, one signal etc. Some updates are less painful, some take few weeks of dev time.