Michał Matyas
The current workflow for E2E tests is to rebuild the app every time you run tests. This works for version based release cycles but does not work well with CI/CD and using EAS Updates OTAs the way they're intended.
There's an option to export the bundle for Android and iOS with
expo export
but there's no way to feed it to the app easily. The manifest is not compatible, the EAS Updates expects update server to be implemented etc. The only way to have this running is by running
expo start
and hoping the bundle will build in enough time for the E2E test to pick it up which is not reliable.
It would be great if there was an easy option to:
  • Prebuild the JS bundle with an option to cache it in CI
  • Feed this prebuilt bundle with assets to the expo-dev-client version of the app (minimal updates server that outputs the same manifest.json as the dev one)
This would allow running Maestro tests over the app on every PR instead of on every App Store release.