Cannot get property 'reactNative' on extra properties extension as it does not exist
See original GitHub issuebug report
Building on iOS works perfectly. However, attempts to build and run on an android device or simulator results in a build error.
$> yarn add react-native-view-shot
$> react-native run-android
BUILD FAILED in 5s
error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.
* Where:
Build file '/Users/ryanbaldwin/src/github.com/Shopify/arrive-client/node_modules/react-native-view-shot/android/build.gradle' line: 50
* What went wrong:
A problem occurred evaluating project ':react-native-view-shot'.
> Cannot get property 'reactNative' on extra properties extension as it does not exist
* 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
BUILD FAILED in 5s
at checkExecSyncError (child_process.js:603:11)
at execFileSync (child_process.js:621:15)
at runOnAllDevices (/Users/ryanbaldwin/src/github.com/Shopify/arrive-client/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:94:39)
at buildAndRun (/Users/ryanbaldwin/src/github.com/Shopify/arrive-client/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:158:41)
at /Users/ryanbaldwin/src/github.com/Shopify/arrive-client/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/index.js:125:12
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Command.handleAction (/Users/ryanbaldwin/src/github.com/Shopify/arrive-client/node_modules/@react-native-community/cli/build/index.js:164:9)
Version & Platform
react-native-view-shot@3.1.1 react-native 0.61.2
Platform: Android
Expected behavior
I expect it to build. 😉
Actual behavior
I does not build. 😦
Steps to reproduce the behavior
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Android build error "extra properties extension" #2627 - GitHub
A problem occurred evaluating project ':react-native-reanimated'. Cannot get property 'react' on extra properties extension as it does not exist.
Read more >Cannot get property 'ndkVersion' on extra properties extension ...
The solution is to create a brand new React Native project (better to create with the same bundle id/name as your current) and...
Read more >react-native-reanimated'. > cannot get property 'react' on extra ...
a problem occurred evaluating project ':react-native-reanimated'. > cannot get property 'react' on extra properties extension as it does not exist.
Read more >Android build error "extra properties extension" "react-native ...
MissingPropertyException : Cannot get property 'react' on extra properties extension as it does not exist. What went wrong:.
Read more >[Solved]-Cannot get property 'ndkVersion' on extra properties ...
Coding example for the question Cannot get property 'ndkVersion' on extra properties extension as it does not exist with... react-native 0.64.0-Reactjs.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I should note that doing a
yarn add react-native-view-shot@3.0.2
instead ofyarn add react-native-view-shot
does not produce this issue.I think that’s what https://github.com/gre/react-native-view-shot/commit/4a2317edee1ba0d434ad00e859cb663074bc2121 has fixed? i’ll need to deploy a patch