Skip to main content
Answered

intercom-react-native:packageDebugResources FAILED

  • 21 July 2023
  • 1 reply
  • 1293 views

Intercom is not compatible React Native versions above 0.70. A `gradle build` command results in the following error. I verified this by using the Intercom example app. Any help, patch, etc that would work would be greatly appreciated as this is blocking us right now in a huge way. 

 Task :intercom-react-native:packageDebugResources FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Some problems were found with the configuration of task ':intercom-react-native:packageDebugResources' (type 'MergeResources').
  - Gradle detected a problem with the following location: '/Users/kevinlint/Concreit/code/fund-mobile-app/node_modules/@intercom/intercom-react-native/android/build/generated/res/rs/debug'.

    Reason: Task ':intercom-react-native:packageDebugResources' uses this output of task ':intercom_intercom-react-native:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

    Possible solutions:
      1. Declare task ':intercom_intercom-react-native:compileDebugRenderscript' as an input of ':intercom-react-native:packageDebugResources'.
      2. Declare an explicit dependency on ':intercom_intercom-react-native:compileDebugRenderscript' from ':intercom-react-native:packageDebugResources' using Task#dependsOn.
      3. Declare an explicit dependency on ':intercom_intercom-react-native:compileDebugRenderscript' from ':intercom-react-native:packageDebugResources' using Task#mustRunAfter.

    Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/Users/kevinlint/Concreit/code/fund-mobile-app/node_modules/@intercom/intercom-react-native/android/build/generated/res/resValues/debug'.

    Reason: Task ':intercom-react-native:packageDebugResources' uses this output of task ':intercom_intercom-react-native:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

    Possible solutions:
      1. Declare task ':intercom_intercom-react-native:generateDebugResValues' as an input of ':intercom-react-native:packageDebugResources'.
      2. Declare an explicit dependency on ':intercom_intercom-react-native:generateDebugResValues' from ':intercom-react-native:packageDebugResources' using Task#dependsOn.
      3. Declare an explicit dependency on ':intercom_intercom-react-native:generateDebugResValues' from ':intercom-react-native:packageDebugResources' using Task#mustRunAfter.

    Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/8.0.1/userguide/command_line_interface.html#sec:command_line_warnings

 

Best answer by Racheal

Hey @Kevin Lint Racheal from the support engineer team here👋 

 

Thanks for providing your logs, this is super helpful for us to have! It looks like your team wrote into support and are working with my teammate Paul on this. I’ll let Paul take it from here, you’re in good hands! He has opened an issue with our engineers and will keep you all posted with any and all updates. I’ll also update here once there is a solution.

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

1 reply

Racheal
Intercom Team
Forum|alt.badge.img+5
  • Customer Support Engineer
  • 512 replies
  • Answer
  • July 27, 2023

Hey @Kevin Lint Racheal from the support engineer team here👋 

 

Thanks for providing your logs, this is super helpful for us to have! It looks like your team wrote into support and are working with my teammate Paul on this. I’ll let Paul take it from here, you’re in good hands! He has opened an issue with our engineers and will keep you all posted with any and all updates. I’ll also update here once there is a solution.


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