-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
auto-detect apk path is not respected if multiple variants configured in configs #60
Comments
Hey, interesting bug. I'm not sure there is any mapping or guarantee between the What would be the expected behavior of detecting and matching configs and variants? |
Sorry it took so long to look at this bug. This feature isn't supported. I could build it if needed, but maybe additionalTestApks is a better option? https://runningcode.github.io/fladle/configuration/#additionaltestapks |
Hey sorry this took a while to get a real response. I took a first stab at this and realized it is impossible to know if the variants should auto-detect the apk since they will already have the apk set and configured from the root. |
So, is it not possible to have the I have a small project here where it does not select the right apks. |
Setting `variant` under `configs` doesn't seem to work: runningcode/fladle#60
Setting `variant` under `configs` doesn't seem to work: runningcode/fladle#60
Running
runFlankOne
orrunFlankTwo
is expected to get the rightapp
andtest
path however it will choose a random variant during auto-detectionThe text was updated successfully, but these errors were encountered: