trynig to install an apk app using Adb prompt cmd :
C:\adb\platform-tools> .\adb install "C:\adb\platform-tools\myapp.apk"
Performing Streamed Install
and than it says :
adb: failed to install C:\adb\platform-tools\myapp.apk: Failure [INSTALL_FAILED_BLOCKED_CROSS_DOWN: INSTALL_FAILED_BLOCKED_CROSS_DOWN]
PS : i used the adb cmd because the app won't install in normal methode (incompatible device)
my device is samsung A20 .
In my case, I had an incorrectly signed application.
I cleared the project and generated the signed application again and the problem was gone
Related
I am trying to build Fuchsia OS and run it on the Fuchsia Emulator femu, but after waiting for the emulator to start the fx command exists and displays the error below.
failed to create Fuchsia device device health check failed. Unable to ssh due to error:
Error: Cannot start Fuchsia Emulator. Exit status is 1
I have followed the instructions provided by Google at fuchsia.dev, the build completes successfully and the commands used to build the OS were
fx set core.qemu-x64 --with //examples/hello_world
fx build
Subsequently, I tried running in headless mode with fx vdl start -N --headless which results in the same error as above, I also tried build the OS without the --with argument but received the same error.
The log file gives us more details, the second last line of the log file may be of interest and it reads:
emu-system-x86_64-headless: network script /etc/qemu-ifdown failed with status 256
I am using Ubuntu 21.04 on my machine.
It seems that the network configuration scripts /etc/qemu-ifup and /etc/qemu-ifdown are missing. You can work around it by installing the qemu package:
$ sudo apt install qemu
I have a nativescript application in windows that deploys to the emulator just fine, but when I git clone onto the MacBook Pro and run the same process, I get:
new-host:nativescript jbaird$ tns run android
Searching for devices...
Starting Android emulator with image Nexus_5X_API_26
Waiting for emulator device initialization...
Executing before-liveSync hook from /Users/jbaird/Documents/development/gr8dates/Nativescript/hooks/before-liveSync/nativescript-angular-sync.js
Executing before-prepare hook from /Users/jbaird/Documents/development/gr8dates/Nativescript/hooks/before-prepare/nativescript-dev-typescript.js
Found peer TypeScript 2.4.2
Preparing project...
Project successfully prepared (Android)
Building project...
Unable to apply changes on device: emulator-5554. Error is: spawn EACCES.
Executing after-watch hook from /Users/jbaird/Documents/development/gr8dates/Nativescript/hooks/after-watch/nativescript-dev-typescript.js
Any ideas? Thanks in advance.
The error is a permission error. Therefore, all you need to do is give access to the the folder you are running your apps from. The process involves you to copy and paste the command below into your terminal.
sudo chmod -R a+rwx /AppFolder
The command is an administrator command, therefore, you may have to insert your system password.
PS: Definitely, you hit enter and there will be a prompt for you to insert your password.
Let me know if you have any challenges with this solution!
emulator-5554. Error is: spawn EACCES.emulator-5554. Error is: spawn EACCES.
Seems a permission error. You could solve it by:
sudo,
Or, by giving +x permision to your hooks folder?
I cannot get rid of this error:
W/PackageManager: Not granting permission android.permission.CAMERA to package because it was previously installed without
This error is preventing me from accessing the camera from my app. I tried uninstalling the apk with adb uninstall and I get:
Failure [DELETE_FAILED_INTERNAL_ERROR]
I then tried changing the package name to install a new apk. I still get the same error in the new app. Any suggestions would be appreciated.
Try with rebooting AT device because
Dangerous permissions requested by apps are not granted until the next device reboot.This includes new app installs and new elements in existing apps.
see AT Release Note
Also, You can install application with granting permission using adb command line as below
adb install -g yourapk.apk
If you have rebooted and the Permissions issue(s) still exist, do the following steps:
Reboot
Connect via adb: adb connect Android.local:5555
Uninstall the apk: adb uninstall (you package name)
reboot
install your apk
reboot
Happy Coding!
I wrote a bash file to start an emulator and install apk with the commands,
emulator -avd emulatorName
adb wait-for-device
adb install OpenManager.apk
but when i run the file from terminal it starts the emulator and it hangs there it doesn't execute the command to install the apk. But when i close the emulator then it execute the install command. Please, can someone help on how to do that.
Add an & to run the emulator process in the background:
emulator -avd emulatorName & adb wait-for-device && sleep 5 && adb install OpenManager.apk
and the && to run the following command if the previous succeeded.
I just installed the android sdk (3.0) on my Mac 10.6.3. I started the emulator successfully using
./emulator -avd my_android &
However, when I try and run a forward command using adb, I get the following error ...
davea-mbp2:platform-tools davea$ ./adb forward tcp:8080 tcp:8080
* daemon not running. starting it now on port 5037 *
* daemon started successfully
error: device offline
Does anyone know what the error means? My emulator is up and running (http://screencast.com/t/bD8WYjZ1) when I run the above command, - Dave
This is an old question but anyway - just had the same issue.
I eventually fixed it by deleting the device and creating a similar one with another name. Recreating the device with the same name did not do the trick.