expo: [docs] Some Constants.manifest fields are not available until update is downloaded when building managed app on EAS Build
Summary
Based on the discussion in https://github.com/expo/sentry-expo/issues/168, it seems that EAS build is using a version of the bare workflow rather than the managed workflow. This isn’t clear from the docs and following the instructions on the normal Constants doc page results in a standalone build that crashes on startup because Constants.manifest.extra is null.
I was able to fix the crash by switching to using the implementation described here but this page isn’t obvious to find and the crash is difficult to debug since it only happens on standalone builds. I didn’t test if following the bare workflow instructions on the first page would resolve the issue as well.
I think that at the very least the docs on the Constants page should be updated to reflect the fact that the steps detailed there won’t work on EAS as written. Happy to make a PR for that change if desired.
Link to the related docs page
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 23 (10 by maintainers)
my concern is that this would just be a game of whack a mole - this is the issue that you encountered, but there are maybe a hundred more that could have caused you similar problems depending on what you are using in your app. maybe the best approach here is for us to more strongly discourage use of eas build with managed apps right now. it is not our intention for people to be using eas build with managed apps at the moment
Got it, I think this can be resolved in the short term by updating this line to say
bare React Native app or using EAS Build. I tried to make a PR but it seems like those install instructions are autogenerated or something so I can’t just update the markdown.It might also be helpful to state some version of your comment on the EAS Limitations page so that it’s clear that you might need to follow bare workflow instructions.