Skip to content
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

Unknown failure cmd: Can't find service: package #24725

Closed
hidayatridwan opened this issue May 7, 2019 · 14 comments
Closed

Unknown failure cmd: Can't find service: package #24725

hidayatridwan opened this issue May 7, 2019 · 14 comments
Labels
Bug Resolution: Locked This issue was locked by the bot.

Comments

@hidayatridwan
Copy link

hidayatridwan commented May 7, 2019

Task :app:installDebug
09:08:07 V/ddms: execute: running am get-config
09:08:07 V/ddms: execute 'am get-config' on 'emulator-5554' : EOF hit. Read: -1
09:08:07 V/ddms: execute: returning
Installing APK 'app-debug.apk' on 'Nexus_5X_API_28_x86(AVD) - 9' for app:debug
09:08:07 D/app-debug.apk: Uploading app-debug.apk onto device 'emulator-5554'
09:08:07 D/Device: Uploading file onto device 'emulator-5554'
09:08:07 D/ddms: Reading file permision of D:\react-native\Kemenkop\android\app\build\outputs\apk\debug\app-debug.apk as: rwx------
09:08:08 V/ddms: execute: running pm install -r -t "/data/local/tmp/app-debug.apk"
09:08:08 V/ddms: execute 'pm install -r -t "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
09:08:08 V/ddms: execute: returning
Unable to install D:\react-native\Kemenkop\android\app\build\outputs\apk\debug\app-debug.apk
com.android.ddmlib.InstallException: Unknown failure (cmd: Can't find service: package)
.
.
.
Task :app:installDebug FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':app:installDebug'.

com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: Unknown failure (cmd: Can't find service: package)

  • 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 1m 1s
62 actionable tasks: 1 executed, 61 up-to-date
Could not install the app on the device, read the error above 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.bat installDebug

Error: Command failed: gradlew.bat installDebug
at checkExecSyncError (child_process.js:637:11)
at Object.execFileSync (child_process.js:655:13)
at runOnAllDevices (D:\react-native\Kemenkop\node_modules\react-native\local-cli\runAndroid\runAndroid.js:299:19)
at buildAndRun (D:\react-native\Kemenkop\node_modules\react-native\local-cli\runAndroid\runAndroid.js:135:12)
at isPackagerRunning.then.result (D:\react-native\Kemenkop\node_modules\react-native\local-cli\runAndroid\runAndroid.js:65:12)
at processTicksAndRejections (internal/process/task_queues.js:86:5)

@react-native-bot
Copy link
Collaborator

Can you run react-native info and edit your issue to include these results under the Environment section?

If you believe this information is irrelevant to the reported issue, you may write `[skip envinfo]` alongside an explanation in your Environment: section.

@andreialecu
Copy link

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.

@hidayatridwan
Copy link
Author

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.

it works thankyou so muchhh!!!

@marcosbarbosa031
Copy link

marcosbarbosa031 commented Jun 4, 2019

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.

Is there a way to make it coldboot by default?

@satty82
Copy link

satty82 commented Jul 8, 2019

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.

Thanks Man it worked for me

@GSLiTW
Copy link

GSLiTW commented Aug 21, 2019

It worked for me THANKS!

@JeyaNandhana
Copy link

Thank you. It worked for me.

@sunnylnct007
Copy link

Works with cold boot. But is this a bug?

@kdhiren
Copy link

kdhiren commented Sep 27, 2019

@andreialecu is correct by selecting Cold boot it works fine, but again change it to Quick boot it wont works. Can it be consider as bug ?

@purushottam-cyber
Copy link

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.
thanks bro it did really helped me out

@viky293
Copy link

viky293 commented Oct 8, 2019

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.

I just wonder how do we reach to such solutions, is it just experience with hit and try methods or there are useful error messages that are ignored by most of us. This is such a time waste for developers.

@shubi100
Copy link

Thanks bro it is working well and solid.

@Mohammed-deve
Copy link

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.

Thanks Man it worked for me

1 similar comment
@Mohammed-deve
Copy link

I just ran into the same error. In my case the emulator was frozen. I had to go to AVD Manager in Android Studio and run "Cold Boot Now" on the specific emulator to get it back up, then this error went away.

Thanks Man it worked for me

@facebook facebook locked as resolved and limited conversation to collaborators May 7, 2020
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label May 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests