ADB exited with exit code 1

18
votes

I'm getting the following error when running my flutter project on Android Emulator. It works fine on iOS Simulator and the project is also fine on my other Mac (runs on both Android and iOS Simulator)

Error: ADB exited with exit code 1 Performing Streamed Install

adb: failed to install /Users/xxxx/Dropbox/Flutter/test_app/build/app/outputs/apk/app.apk: Error launching application on Android SDK built for x86.

I've cleaned my project and reset my emulator but no luck. It only affects my mac book pro android build.

Flutter doctor also shows no issues

[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Mac OS X 10.14.5 18F132, locale en-CA)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[!] iOS toolchain - develop for iOS devices (Xcode 10.2.1)
    ✗ Verify that all connected devices have been paired with this computer in Xcode.
      If all devices have been paired, libimobiledevice and ideviceinstaller may require updating.
      To update with Brew, run:
        brew update
        brew uninstall --ignore-dependencies libimobiledevice
        brew uninstall --ignore-dependencies usbmuxd
        brew install --HEAD usbmuxd
        brew unlink usbmuxd
        brew link usbmuxd
        brew install --HEAD libimobiledevice
        brew install ideviceinstaller
[✓] Android Studio (version 3.4)
[✓] Connected device (2 available)
10
androidflutter
what is your package name ? – dariush f

10 Answers

42
votes

I know two reason that lead to this error :

  • Maybe your device/emulator's storage is full. Try deleting some apps or similar to free up storage.

Or

  • Invalid package name . for example using capital letter in package name. use this to change package name in flutter
18
votes

I run flutter clean every time I get this and it seems to fix it.

6
votes

Allow 'installing apps from usb' on your phone if you get this error on physical device

6
votes

for my phone (not emulator) i disabled Verify apps over USB from developer options from my phone settings and it works.

5
votes

For me, everything worked after I deleted the build directory inside my flutter project. The build should have the app.apk binary file.

  1. Delete that file or delete the whole build folder and run your project.
  2. If that doesn't work, just delete your AVD emulator completely and start a new one.
4
votes

This error will be appear when your device hasnt enough storage for installing the application if you work with Flutter, android studio doesnt tell exact problem.

1
votes

I have been struggling with this off and on for a year, here is what I just noticed that makes it work or not work on my system.

I discovered tonight that if I have my virus protection running my emulator stalls in the
" ---> Built build\app\outputs\apk\debug\app-debug.apk. and I just get a white screen. I turn off the virus protection and it works fine in debug mode. If its on I have to keep going to the terminal and doing: " flutter run " to see any changes I have made. Maybe this will help someone.

0
votes

Google service scans apk and consider it harmful and block from installation

Disable/ turn off the google service app scan. in your emulator

0
votes

If you have previously installed apps on your Android Emulator,
Try uninstalling some already installed apps from the Android Emulator by going to...

Settings >> Apps & notifications >> app_to_be_uninstalled >> Uninstall

It worked for me :)

0
votes

To debug this, on Android Studio, open the Logcat tab. You will get a ton of messages, but somewhere in there will be the answer.

For example, if the package name is invalid, you will see:

W/ActivityManager: Invalid packageName: your.bad.package.name

Try using the search field in the upper right of the logcat window to filter the messages.

Also, you need to make sure that the device you are working with is selected in the target dropdown at the top of the window. Often, if you get this error, Android Studio will automatically remove your device from the target list and switch it to a different device. You might have to unplug and plug back in your USB cable to get it to appear again. Then select it, and open the Logcat tab at the bottom. The messages from the previous session will be saved and you can look through them.