Failed resolution of: Lcom/facebook/yoga/YogaConfigFactory

[xfumihiro]

I'm getting this error while using Litho (0.33.0) with RN (0.61.5)

React Native version: 0.61.5

System:
OS: macOS Mojave 10.14.6
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 144.97 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.14.0 - ~/.nvm/versions/node/v12.14.0/bin/node
Yarn: 1.19.1 - /usr/local/bin/yarn
npm: 6.13.4 - ~/.nvm/versions/node/v12.14.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 26, 27, 28, 29
Build Tools: 28.0.3, 29.0.2
System Images: android-28 | Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.6010548
Xcode: 11.3/11C29 - /usr/bin/xcodebuild
npmPackages:
react: 16.12.0 => 16.12.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
react-native-cli: 2.0.1

Steps To Reproduce

1. setup RN with react-native init
2. add litho dependencies (followed steps here)
3. create custom LithoView instance and run

note:
excluded deps as suggested

configurations.all {
  exclude group: 'com.facebook.yoga', module: 'yoga'
//   exclude group: 'com.facebook.infer.annotation', module: 'infer-annotation'
  exclude group: 'com.google.code.findbugs', module: 'jsr305'
}

had to comment out excluding infer-annotation module because of the error:
java.lang.NoClassDefFoundError: Failed resolution of: Lcom/facebook/infer/annotation/Assertions

Describe what you expected to happen:
be able to use Litho with RN

Snack, code example, screenshot, or link to a repository:

https://github.com/xfumihiro/rn_issue_with_litho

related issues
facebook/litho#522
facebook/litho#565
#24459

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.