bitrise-steplib/bitrise-step-android-build

Detox build fails

benmechen opened this issue · 3 comments

benmechen commented

We are running this step on our workflow and are facing this issue. The solution is to prepend the gradlew command with app: like so:
./gradlew app:assembleRelease app:assembleAndroidTest

How can we do this on the bitrise android build step?

Error from build step

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':expo-permissions:mergeLibDexDebugAndroidTest'.
> Could not resolve all files for configuration ':expo-permissions:debugAndroidTestRuntimeClasspath'.
   > Failed to transform classes.jar (project :unimodules-permissions-interface) to match attributes {artifactType=android-dex, com.android.build.api.attributes.BuildTypeAttr=debug, com.android.build.api.attributes.VariantAttr=debug, com.android.build.gradle.internal.dependency.AndroidTypeAttr=Aar, dexing-enable-desugaring=false, dexing-is-debuggable=true, dexing-min-sdk=21, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime, org.jetbrains.kotlin.platform.type=androidJvm}.
      > Execution failed for DexingNoClasspathTransform: /Users/ben/Documents/Work/FootballExchange/node_modules/unimodules-permissions-interface/android/build/intermediates/runtime_library_classes/debug/classes.jar.
         > Error while dexing.
   > Failed to transform classes.jar (project :unimodules-core) to match attributes {artifactType=android-dex, com.android.build.api.attributes.BuildTypeAttr=debug, com.android.build.api.attributes.VariantAttr=debug, com.android.build.gradle.internal.dependency.AndroidTypeAttr=Aar, dexing-enable-desugaring=false, dexing-is-debuggable=true, dexing-min-sdk=21, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for DexingNoClasspathTransform: /Users/ben/Documents/Work/FootballExchange/node_modules/@unimodules/core/android/build/intermediates/runtime_library_classes/debug/classes.jar.
         > Error while dexing.
chaitanyatanna-bitrise commented

Hi @benmechen
You would be able to do the above using the Script Step in the workflow

Thanks
Chaitanya

github-actions commented

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant.
This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

github-actions commented

I'll close this issue as it doesn't seem to be relevant anymore.
We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.