expo: Android build fails on createReleaseExpoManifest

Hey @dondragon2 - we will add a clearer error message here but unfortunately, builds with expo-updates installed do currently require that the metro bundler server is running in another process. The templates from expo init have expo-updates preinstalled because we anticipate most users will want this functionality, but you can remove it if needed.

If you can customize how you start your build and/or have a separate process running in App Center, it shouldn’t be a problem, but if not, you may need to uninstall expo-updates to get the build to run.

It’s on our roadmap to get builds with expo-updates running without the need for a packager server. But that’s unfortunately not the case right now 😞 Sorry for the trouble!

Ok, basically, I looks like I can’t run a separate process with bundler when using Bitrise. Any workarounds?

@brentvatne I am trying to have my builds automated with AppCenter. Currently AppCebter works fine with a regular react native app. But, with Expo bare it fails with the error above. how would we have metro running in this case or what would be a workaround in this case?

@shubhamdeol - i assume you’re following the guide here? https://reactnative.dev/docs/signed-apk-android#generating-the-release-apk

i think that page should be updated to let users know that they need to have the react-native server running 😃 maybe you could open a PR to clarify that

@dondragon2 Sure. I followed the uninstall guide 100%. Other than that, I did not do anything.

Additional info: my project in question was bootstrapped with create react native app.

Still fails on expo-updates@0.2.14 for me

I’ve been debugging this with @brentvatne via slack.

I’m loading SVGs

import someSvg from '$assets/images/some.svg'

to pass to <SvgXml xml={someSvg} … />. We have the following in our babel.config.js:

{
  plugins: [
    ['babel-plugin-inline-import', {extensions: ['.svg']} ],
  ]
}

After removing all of the SVG imports the iOS build runs fine.

Edit

Problem resolved with expo-updates@0.2.13

@shubhamdeol - i assume you’re following the guide here? https://reactnative.dev/docs/signed-apk-android#generating-the-release-apk

i think that page should be updated to let users know that they need to have the react-native server running 😃 maybe you could open a PR to clarify that

yarn android
yarn run v1.21.1
$ react-native run-android

Goes onwards to build the app (for development)

At some point - I am going to assume this is windows related - the node.js (react native) is killed, most likely because a file is being editted by the build process, and when the dev build finishes, the bundler is dead.

Error: EPERM: operation not permitted, lstat 'path\to\android\app\build\generated\assets\react\release\index.android.bundle'
Emitted 'error' event on NodeWatcher instance at:
    at NodeWatcher.<anonymous> (path\to\node_modules\sane\src\node_watcher.js:291:16)
    at FSReqCallback.oncomplete (fs.js:175:21) {
  errno: -4048,
  code: 'EPERM',
  syscall: 'lstat',
  path: 'path\to\\android\\app\\build\\generated\\assets\\react\\release\\index.android.bundle'
}

(The above is what causes the bundler to die – this issue has been present for longer).

⚠️ this has nothing to do with Admin rights, as in, you can’t solve this by running cmd.exe or powershell in administrative mode. ⚠️

You can still “fix” this flow by just running react-native start after your app has started on the device. Kill the app on the devise and start it again.

Now the bundler runs, and you can do gradle bundleRelease.

When gradle bundleRelease kills the bundler (see above), quickly start it again. You usually have about ~1 minute to do this.

@sbecker I have also encountered this problem. I solve this problem by updating my expo-update@0.2.0 to expo-updates@0.2.5 expo-updates@0.2.5