Could not determine the dependencies of task ':intercom_intercom-react-native:compileDebugJavaWithJavac'.

Question

I’ve recently become unable to successfully build for Android with Intercom SDK I’m using "@intercom/intercom-react-native": "^7.0.1",and have configured my app.json / expo properly with  ["@intercom/intercom-react-native",{"appId": "lxxxxxxxxp","androidApiKey": "anxxxxxxxxxxxxxxxx196","iosApiKey": "ioxxxxxxxxxxxxxxxxx29f","intercomRegion": "US","isPushNotificationsEnabledIOS": "true" // I know this is currently unsupported though I did set up my code to push native tokens to intercom as I assume itll get there soon.}],FAILURE: Build failed with an exception.* What went wrong:Could not determine the dependencies of task ':intercom_intercom-react-native:compileDebugJavaWithJavac'.> Could not resolve all dependencies for configuration ':intercom_intercom-react-native:debugCompileClasspath'.   > Problems reading data from Binary store in /Users/joshuamohrer/.gradle/.tmp/gradle11368370330674472490.bin offset 1490991 exists? true* 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.For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.BUILD FAILED in 2m 1s15 actionable tasks: 15 up-to-dateError: /Users/joshuamohrer/Coding/waveapp/android/gradlew exited with non-zero code: 1Error: /Users/joshuamohrer/Coding/waveapp/android/gradlew exited with non-zero code: 1    at ChildProcess.completionListener (/Users/joshuamohrer/Coding/waveapp/node_modules/@expo/cli/node_modules/@expo/spawn-async/build/spawnAsync.js:52:23)    at Object.onceWrapper (node:events:634:26)    at ChildProcess.emit (node:events:519:28)    at maybeClose (node:internal/child_process:1105:16)    at ChildProcess._handle.onexit (node:internal/child_process:305:5)    ...    at Object.spawnAsync [as default] (/Users/joshuamohrer/Coding/waveapp/node_modules/@expo/cli/node_modules/@expo/spawn-async/build/spawnAsync.js:17:21)    at spawnGradleAsync (/Users/joshuamohrer/Coding/waveapp/node_modules/@expo/cli/build/src/start/platforms/android/gradle.js:72:46)    at Object.assembleAsync (/Users/joshuamohrer/Coding/waveapp/node_modules/@expo/cli/build/src/start/platforms/android/gradle.js:52:18)    at runAndroidAsync (/Users/joshuamohrer/Coding/waveapp/node_modules/@expo/cli/build/src/run/android/runAndroidAsync.js:36:24)    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) I’ve built locally and with EAS Build, with the same outcomeI’m using Expo so i cant make changes directly to the android folder. This is my current app.json, I suspect something here needs to change. I adopted these settings after after a ton of trial and error to make everything build with an unrelated SDK.I’m a bit out of my depths with this, so if anyone has any suggestions for changes below, I’d appreciated it! "expo-build-properties",{"android": {"kotlinVersion": "1.6.21","buildToolsVersion": "33.0.1","minSdkVersion": 24,"compileSdkVersion": 34,"targetSdkVersion": 34,"packagingOptions": {"pickFirst": ["org/bouncycastle/x509/CertPathReviewerMessages*"]},"extraMavenRepos": ["https://maven.google.com","https://sdk-download.airbridge.io/maven","https://mvnrepository.com/artifact/io.adapty","https://jitpack.io","../../node_modules/react-native-adapty/lib/android/localMaven","../../node_modules/@adapty/react-native-ui/android/localMaven","../../node_modules/airbridge-expo-sdk/android/maven","../../node_modules/react-native/android"],"kotlinOptions": {"jvmTarget": "17"},"compileOptions": {"sourceCompatibility": "17","targetCompatibility": "17"},

Jacob Cox · Accepted Answer

Hey there @joshmohrerIssues like this are best handled by writing into the actual Support Team. I’m going to send your message over to them and they will reach back out to you via the email address that you signed up with and get more details from you! Keep an eye on your spam inbox just to make sure you don’t miss their message!

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded