Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Execute Detox E2E Tests in Debug Mode #7

Closed
sabuhiteymurov opened this issue Aug 28, 2023 · 0 comments · Fixed by #6
Closed

Unable to Execute Detox E2E Tests in Debug Mode #7

sabuhiteymurov opened this issue Aug 28, 2023 · 0 comments · Fixed by #6

Comments

@sabuhiteymurov
Copy link
Owner

sabuhiteymurov commented Aug 28, 2023

Bug Description

I followed the instructions and attempted to resolve this issue for several days. When running the debug test, I encountered the following error:

Error: No instrumentation runner found on device emulator-19386 for `packageName`

Reproduction Steps

  1. Refer to the official guide for details.
  2. Set binaryPath to bin/expo-base.apk.

The error occurs in e2e/utils/openApp.ts, specifically on this line:

await device.launchApp({ newInstance: true })

I've tested this issue on the latest Detox release, and it still persists.

Steps to Reproduce

  1. Follow the documentation as mentioned earlier.

Expected Behavior

The tests should run without encountering any issues.

Should generate verbose Detox logs, and artifacts

Environment:

  • Detox: latest
  • React Native: 0.72.4
  • Expo: 49.0.8
  • Node: 18
  • Device: emulator
  • Operating System: Ubuntu 22.04
  • Test Runner: jest-circus
@sabuhiteymurov sabuhiteymurov changed the title Error: No instrumentation runner found on device emulator-16982 for package ‘packageName’ Unable to Execute Detox E2E Tests in Debug Mode Aug 28, 2023
@sabuhiteymurov sabuhiteymurov linked a pull request Aug 28, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant