Skip to main content
Answered

React native Android build failed

  • 7 November 2023
  • 2 replies
  • 1489 views

After installing and setting up intercom in a react native project, android build fail.

I’m getting the following error

Execution failed for task ':app:mergeExtDexWatuDebug'.
> Could not resolve all files for configuration ':app:watuDebugRuntimeClasspath'. > Failed to transform play-services-measurement-api-21.4.0.aar (com.google.android.gms:play-services-measurement-api:21.4.0) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=21, org.gradle.status=release, org.gradle.usage=java-runtime}. > Execution failed for DexingWithClasspathTransform: /Users/emmanueltochukwu/.gradle/caches/transforms-3/fceb8847abe1dd3732979c14af3f21a7/transformed/jetified-play-services-measurement-api-21.4.0-runtime.jar. > Error while dexing. > Failed to transform play-services-measurement-api-21.4.0.aar (com.google.android.gms:play-services-measurement-api:21.4.0) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=21, org.gradle.status=release, org.gradle.usage=java-runtime}. > Execution failed for DexingWithClasspathTransform: /Users/emmanueltochukwu/.gradle/caches/transforms-3/fceb8847abe1dd3732979c14af3f21a7/transformed/jetified-play-services-measurement-api-21.4.0-runtime.jar. > Error while dexing. * Try:

Any assistance on this will be appreciated.

Best answer by Jacob Cox

Hey there @emmanuel93 !

This error doesn’t look familiar to me at all and I can’t find anything similar in our logs or repo. Is there a reason why you think this is associated with Intercom?

I would make sure you are following our installation instructions here and looking over the example app that we created, to make sure you have everything set up correctly.

View original
Did this topic help you find an answer to your question?

2 replies

Jacob Cox
Intercom Team
Forum|alt.badge.img+5
  • Sr. Technical Support Engineer
  • 441 replies
  • Answer
  • November 12, 2023

Hey there @emmanuel93 !

This error doesn’t look familiar to me at all and I can’t find anything similar in our logs or repo. Is there a reason why you think this is associated with Intercom?

I would make sure you are following our installation instructions here and looking over the example app that we created, to make sure you have everything set up correctly.


Jacob Cox
Intercom Team
Forum|alt.badge.img+5
  • Sr. Technical Support Engineer
  • 441 replies
  • November 12, 2023

I am seeing a StackOverflow article related to that error. Perhaps it will be helpful?


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings