Incompatible with Gradle Configuration Cache (Build Fails)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, react-native
- Domain
- build-system, mobile
Research direction
Start with android/build.gradle at line 61 and review the configuration-cache setting in gradle.properties. Reproduce the failure with org.gradle.configuration-cache=true and inspect how the NodeJS command is invoked during configuration. Done means the Android build completes without reporting an external process configuration-cache problem.
Written by the indexing model from the issue text.
Description
When org.gradle.configuration-cache is set to true in gradle.properties, builds fail due to react-native-nitro-sqlite executing NodeJS code to get the contents of the react-native package.json file.
FAILURE: Build failed with an exception.
* Where:
Build file 'D:\WebstormProjects\FOX\node_modules\react-native-nitro-sqlite\android\build.gradle' line: 61
* What went wrong:
Configuration cache problems found in this build.
1 problem was found storing the configuration cache.
- Build file '..\node_modules\react-native-nitro-sqlite\android\build.gradle': line 61: external process started 'node --print require.resolve('react-native/package.json')'
See https://docs.gradle.org/9.0.0/userguide/configuration_cache_requirements.html#config_cache:requirements:external_processes
See the complete report at file:///D:/WebstormProjects/FOX/android/build/reports/configuration-cache/9fvn5smucgpiq2rrlzzb5wc72/43utdihyq22dc050e5qm7ci8t/configuration-cache-report.html
> Starting an external process 'node --print require.resolve('react-native/package.json')' during configuration time is unsupported.
- Dominant language
- C
- Stars
- 565
- Forks
- 53
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 28
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from margelo/react-native-nitro-sqlite
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
margelo/react-native-nitro-sqlite#218 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in margelo/react-native-nitro-sqlite
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·