./gradlew app:dependencies fails on `unimodules-core`-related error

[brettdh]

I’m currently trying to resolve Android dependency hell between ExpoKit and react-native-firebase, as described in this topic:

Fresh Detached Expo + RNFirebase not running on Android

Hi, So I’m trying to start an app using the Detached Expokit and React Native Firebase (v3) I made a fresh project with exp cli, followed all the instructions at https://invertase.io/react-native-firebase/ to set up ios, and it runs fine followed all the instructions to set up on android, went through some dependency hell between the expo dependencies and firebase dependencies And now there are no more warnings, and no more errors, but when i try to run the app (either emulator or physical…

and I’m currently trying to run ./gradlew app:dependencies to find the source of a version conflict, but it’s failing on something to do with unimodules-core:

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/brhiggins/src/theliturgists/app/node_modules/@unimodules/core/android/build.gradle' line: 8

* What went wrong:
A problem occurred evaluating project ':unimodules-core'.
> Cannot change dependencies of configuration ':unimodules-core:classpath' after it has been resolved.

Code is here: https://github.com/theliturgists/app/tree/165-push-notifications

Here’s a diff of just the firebase-related changes on this branch: https://github.com/theliturgists/app/compare/165-push-notifications

I have react-native-firebase working fine on iOS, and before the two commits on this branch, I had a working, detached-to-ExpoKit project using Expo SDK 33. Any help would be greatly appreciated.

[brettdh]

Not sure what (if anything) this means, but if I comment out this line (and the addUnimodulesDependencies call later in the file), the next implementation() line (react-native-firebase) becomes the one that appears on the above error message.

Same with the two other lines below it (added by react-native link, IIRC). If I remove all three, stopping at fileTree, then app:dependencies succeeds. It doesn’t expose the conflicting version, though, which I think tells me that one of those three packages is (indirectly) responsible.

Really shooting in the dark here.

[brettdh]

Couldn’t tell you exactly why, but this commit seems to have fixed my underlying version clashes:

https://github.com/theliturgists/app/commit/ed705f337820cae85f0cce409e9e4d651f56d750

However, the app:dependencies issue remains. I was able to run it if I commented out the lines I mentioned above, and sometimes I also had to comment out the google-services plugin line at the end of build.gradle - but even with the dependency tree, I was doing guesswork at best, and it seems like I just got lucky. I would still love to understand what’s going on here (both issues), and whether I’m making it more difficult than it needs to be - but maybe the info above can help someone else get unstuck.