-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Android: '-androidTest.apk' seems to get appended to a valid apk path #830
Comments
Hi Run this and try : once succeed then check apk at android/app/build/outputs/apk/debug/app-debug.apk Then run following Node : this is for debug build Following is my version: |
Hi Team, When you want to test on debug build which is not placed under androidTest folder then Detox search by default under androidTest folder rather than given binary path. This is an issue I am facing. Error :
package.json entry: |
@yamiscott Any workaround till this get fix? |
Hi Just want to update you that I have changed following in APKPath.js at line no 22
And following is the binarypath in package.json "binaryPath": "android/app/build/outputs/apk/debug/my.project-universal-debug.apk", |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
The issue has been closed for inactivity. |
Description
Using Detox 8, if I set up an android build and get the detox build to successfully create the apk I need. Then set package json configuration for the android test to point at this apk and run detox test. Detox errors looking for the apk as it adds '-androidTest.apk' to the end of the path (stripping the existing .apk extension), resulting in never being able to run tests against that file.
apk file path (excluding personal path elements):
package.json config:
error:
The problem is inside APKPath.js line 23
As you can see (well you can if you head into the file), it splits on the last '-' and grabs the extension, then drops the 'variant' assuming it to be '-debug' or '-release', but without flavours, this isn't the case with a standard project.
It then rebuilds the path assuming the path is a flavoured build. Then finally it blanket adds a -androidTest on the end. Resulting in the error I'm seeing.
Steps to Reproduce
Basically follow the tutorial.
Detox, Node, Device, Xcode and macOS Versions
Device and verbose Detox logs
The text was updated successfully, but these errors were encountered: