Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
unimodules-react-native-adapter:compileDebugJavaWithJavac FAILED
See original GitHub issueSummary
Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!
bare
What platform(s) does this occur on?
Android
SDK Version (managed workflow only)
No response
Environment
Expo CLI 4.5.2 environment info: System: OS: Windows 10 10.0.19043 Binaries: Node: 14.17.0 - C:\Program Files\nodejs\node.EXE npm: 6.14.13 - C:\Program Files\nodejs\npm.CMD IDEs: Android Studio: Version 4.2.0.0 AI-202.7660.26.42.7351085 npmPackages: expo: ^41.0.0 => 41.0.0 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: ~0.63.4 => 0.63.4 react-native-web: ~0.13.12 => 0.13.18 Expo Workflow: bare
Reproducible demo or steps to reproduce from a blank project
I was working on ubuntu before, I changed switched to windows and ran :
npm i
npm run android
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:33 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 After updating to Expo SDK 42
@wbroek - something changes about the semantics when you run
./gradlew clean assembleReleasevs invoking the commands in two separate calls:this works as expected. do you happen to have any idea what the difference is between these approaches? we run the module list generation prior to gradle preBuild: https://github.com/expo/expo/blob/a3f3a9a724bfef6c351dc378258649b3769aaee7/packages/%40unimodules/react-native-adapter/android/build.gradle#L59