-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run android #2515
Comments
Thanks for raising this issue. Can you clarify if you are trying to run react-native-windows on an android device? |
I can run react-native run-android in project react-native-windows ? |
Hi 😃 I ran on my cmd.exe
and then #2515 (comment) error mesesage shew. 😭 |
Exactly the same issue here. Exactly as reepias and aiya000 explain, running the windows command, opens up the windows emulator correctly and runs the app correctly too. When running react-native run-android command, then we get this error message. |
@reepias It's 6 days ago you reported this, did you have any progress by any chance? |
Following |
@rozele , @in4margaret - can one of you take a look to see what's going on? Looks like its an issue in the |
It's happening in the |
Oh, thanks for clarifying @MakhouT . Let me circle back with the crew and see if we can get to the bottom of this as soon as possible. |
( I'm on |
Here's what's going on : the The problem you are hitting is because we have added code to this fork for improving the windows story (keyboarding, mouse hover, accessibility etc.,) which is conflicting with the base react-native implementation and hence it is not in a great state for xplat development right now. We are tracking the cleaning up of the Until these tasks are done, there are 2 possible options for xplat development (running on android/iOS while developing/running on Windows as well):
Work-around details:
When building for iOS/Android, point dependencies to react-native and start scripts to react-native CLI:
|
Thanks for clarifying this @harinikmsft |
Closing this issue as the main underlying issues are being tracked by #2535 and #2264 as mentioned in the above comment. I will submit a PR shortly where this is being referenced in the troubleshooting section of the vnext Getting Started Guide |
Happy to report that we have addressed the underlying issues here and validated internally. You no longer need the above workarounds to add react-native-windows to your RN projects. You can stay on the main facebook/react-native fork and simply add react-native-windows and things should work! tagging : @MakhouT , @aiya000 , @dlwsacrez, @reepias so you see this update. Thanks for flagging this! Let us know if you still see issues after removing the workaround from earlier. |
Cool!! Happy to hear! Nice progress guys! |
problem
JS server already running.
Building and installing the app on the device (cd android
&& ./gradlew installDebug)...
FAILURE: Build failed with an exception.
Execution failed for task ':app:compileDebugJavaWithJavac'.
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 4s
15 actionable tasks: 7 executed, 8 up-to-date
Could not install the app on the device, read the error ab
ove for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html
Command failed: ./gradlew installDebug
Error: Command failed: ./gradlew installDebug
at checkExecSyncError (child_process.js:631:11)
at Object.execFileSync (child_process.js:649:15)
at runOnAllDevices (/Users/namprik/Projects/React-Native/bplusapp/node_modules/react-native/local-cli/runAndroid/runAndroid.js:299:19)
at buildAndRun (/Users/namprik/Projects/React-Native/bplusapp/node_modules/react-native/local-cli/runAndroid/runAndroid.js:135:12)
at /Users/namprik/Projects/React-Native/bplusapp/node_modules/react-native/local-cli/runAndroid/runAndroid.js:65:12
at processTicksAndRejections (internal/process/task_queues.js:89:5)
This is my react environment
React Native Environment Info:
System:
OS: macOS 10.14.4
CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 42.12 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.1.0 - /usr/local/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 23, 24, 25, 26, 27, 28
Build Tools: 23.0.1, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.3, 28.0.2, 28.0.3
System Images: android-23 | Intel x86 Atom, android-23 | Intel x86 Atom_64, android-23 | Google APIs ARM EABI v7a, android-23 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-24 | ARM 64 v8a, android-24 | ARM EABI v7a, android-24 | Intel x86 Atom, android-24 | Intel x86 Atom_64, android-24 | Google APIs ARM EABI v7a, android-24 | Google APIs Intel x86 Atom_64, android-24 | Google Play Intel x86 Atom, android-25 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-P | Intel x86 Atom_64, android-P | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5264788
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: https://github.com/microsoft/react-native/archive/v0.58.6-microsoft.48.tar.gz => 0.58.6-microsoft.48
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
The text was updated successfully, but these errors were encountered: