Unable to build a dev client for Android and successfully use it

[trajano]

Summary

I tried a few permutations on getting the dev client to build. On Windows run:android just gets stuck at config-syncing. I have a Android dev-client built successfully on macOS and on a Linux build server.

When I use the Linux built one, and try to launch my app using expo start --dev-client I get

Attempting to call JS function on a bad application bundle: AppRegistry.runApplication()

Unfortunately there's no logs.

The macOS one yields different errors so I'll create a separate bug for that one.

What platform(s) does this occur on?

Android

Environment

  expo-env-info 1.0.5 environment info:
    System:
      OS: Windows 10 10.0.22000
    Binaries:
      Node: 16.15.1 - ~\.nvm\versions\node\v16.15.1\bin\node.EXE
      Yarn: 1.22.19 - ~\.nvm\versions\node\v16.15.1\bin\yarn.CMD
      npm: 8.11.0 - ~\.nvm\versions\node\v16.15.1\bin\npm.CMD
    IDEs:
      Android Studio: AI-212.5712.43.2112.8815526
    npmPackages:
      @expo/metro-config: ^0.3.12 => 0.3.21
      babel-preset-expo: ~9.1.0 => 9.1.0
      expo: ^45.0.0 => 45.0.6
      react: 17.0.2 => 17.0.2
      react-dom: 17.0.2 => 17.0.2
      react-native: 0.68.2 => 0.68.2
      react-native-web: 0.17.7 => 0.17.7
    Expo Workflow: bare

It says bare per brents recommendation to run:android but I am normally on managed and I reset it back to get back to managed.

Minimal reproducible example

not available.

[trajano]

After reverting back to my HEAD branch I get managed again

  expo-env-info 1.0.5 environment info:
    System:
      OS: Windows 10 10.0.22000
    Binaries:
      Node: 16.15.1 - ~\.nvm\versions\node\v16.15.1\bin\node.EXE
      Yarn: 1.22.19 - ~\.nvm\versions\node\v16.15.1\bin\yarn.CMD
      npm: 8.11.0 - ~\.nvm\versions\node\v16.15.1\bin\npm.CMD
    IDEs:
      Android Studio: AI-212.5712.43.2112.8815526
    npmPackages:
      @expo/metro-config: ^0.3.12 => 0.3.21
      babel-preset-expo: ~9.1.0 => 9.1.0
      expo: ^45.0.0 => 45.0.6
      react: 17.0.2 => 17.0.2
      react-dom: 17.0.2 => 17.0.2
      react-native: 0.68.2 => 0.68.2
      react-native-web: 0.17.7 => 0.17.7
    Expo Workflow: managed

[expo-bot]

Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue.

The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue.

A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own.

Resources

• "How to create a Minimal, Reproducible Example"
• "How to narrow down the source of an error"

Common concerns

"I've only been able to reproduce it in private, proprietary code"

You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase.

"I didn't have time to create one"

That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template.

"You can reproduce it by yourself by creating a project and following these steps"

This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue.

[Kudo]

hi there! i tried expo-cli run:android on windows and it works for me. it's hard for further investigation without more details or minimal reproducible example. you could also try to pass EXPO_DEBUG for more debug information when running run:android, i.e. EXPO_DEBUG=1 expo-cli run:android.

[trajano]

Thanks the EXPO_DEBUG=1 would help.

I am closing this now since I found the problem but only when I did --tunnel since it didn't say what the error is aside from network error on the logs

Also I had to use logcat to determine the issues, the errors didn't appear in the console logs.