I have already installed qemu-kvm on my device and also give a current user & root user permission on kvm group.
When I open AVD manager and launch AVD in emulator it works!!
But when I run my android project it still shows the error.
[ERROR 1]
and also when I choose connected device than it also shows an error:
[ERROR 2]
Session 'app':Error installing apk whereas I did checked:usb debugging in my phone and unchecked:Enable instant run in android studio setting.
SO how can I solve this problem ?
Any Help is appriciated. Thank you!
Running this command should do it:
sudo adduser $(whoami) kvm
It adds your currently logged-in user to the kvm group. You'll need to logout and log back in for it to take effect
Related
I have an app installed on Android Things, in a Raspberry Pi. I want to replace with a newer version, but it's overwritten with previous version after a reboot. That's weird!
This is what I've tried: Let's say the installed app package name is "com.myapp", I've run "adb uninstall com.myapp", and I get "Success". If I run uninstall command again, I get "Failure [DELETE_FAILED_INTERNAL_ERROR]", so the app is completely uninstalled.
Then, I've modified package name in build.gradle to "com.mynewapp", and I install and run it using Run button from Android Studio. Now "com.mynewapp" appears when I run "adb shell pm list packages".
Now I restart the Pi using "adb shell reboot". And after reboot, the old app is running. Executing "adb shell pm list packages" shows my old package: "com.myapp", and "com.mynewapp" does not appear in the list.
How can I completely remove the old app, and replace with a new one?
Uninstall the app using:
adb uninstall <pkg name>
I tried deleting all SD contents, and flash latest Android Things image, and I realized SD card is corrupt. I replaced SD card, and it's working fine.
You can not uninstall the app which you packed in the OS image and flashed in the SD card using adb (returns the error which you encountered Failure [DELETE_FAILED_INTERNAL_ERROR]). Only you can uninstall the app which you installed using adb or android studio.That is why first time you are seeing success,which is uninstalling the overwritten version but next time as you are actually trying to uninstall the OEM version of your app so,you are seeing this error.
Just format and reflash the SD card with only Android things OS (without your app) then install your app using adb/android studio,now you will have only the uninstallable copy of your app in the sd card. So you can replace or do whatever you like with that app as like normal app downloaded from playstore.
I am getting the following error when I run ideviceinstaller/ideviceinfo commands:
No iOS device found, is it plugged in?
My iPhone is certainly plugged is and visible in lsusb.
Restart the usbmuxd service and your device will show up normally:
systemctl restart usbmuxd.service
Your iPhone will vibrate if it connected successfully.
there is a file 'lockdownd' and it might have 0700 permissions with the owner as root. You should try chmod 0705 lockdownd. restart was not necessary for me. You might also run ideviceinstaller/ideviceinfo as root or with sudo. You might not have a recent version or you might have multiple versions installed. There is an xcode version-ish and there is a brew.
UPDATE there are a lot of details missing here, however, I gt this error when I had installed libimodiledevices with brew and allowed or told brew to clean the other dynlinks. That disabled ideviceinfo etc because of a missing dynlib. For example flutter prepackages these tools and brew breaks it.
I am building an iOS project on yosemite with xcode 7.1 on a macbook pro where i login with network (Domain) credentials.
If i do ls -l I can see my files belonging to myuser:24252342423
When Xcode tries to perform the chown command while building the archive it tries to do: chown -RH myuser:MYDOMAIN\\Domain\ Users <filepath>
and that generates an error: chown: MYDOMAIN\Domain\ Users: illegal group name
Any ideas on how to fix it?
The problem was due to me being connected in vpn and thus the groupname was not resolved, once i got back to office the problem was automatically solved.
I'm tryin' to debug my app on iOS simulator in my Mac.
I've followed all the instructions installing on my Mac:
sudo npm install -g vs-mda-remote
sudo npm install -g ios-sim
When I prompted
vs-mda-remote --buildDir Projects
(Projects is the folder where debug files will be droped), I see results in my PC by
http://<MAc_IP>:3000
With the following text
Remote build Express server open for business on port 3000
Ok, now I prompted
vs-mda-remote test
And I see an error with the following message
Failed to build app: CordovaError: Platform ios already added
I don't know what happen.
Ok, I found the problem. Maybe, I'm too eagier.
Instead of using one session in terminal app on mac, I used too many, so, when I prompted too many timesvs-mda-remote, obviously ios was already installed.
So, opening terminal at first time, and prompting
vs-mda-remote --buildDir Projects --allowsEmulate=true
Now, I can debug on iOS simulator from my PC to Mac.
While running the build agent, the correct command is:
vs-mda-remote --buildDir <server-build-directory> --allowsEmulate=true
Note the last "--allowsEmulate=true" part of the command.
*Taken from "Setting up the Remote Agent to Support Starting the iOS Simulator" section in the documentation.
Platform ios already installed
Received this error for running in device too, while running multiple instance in mac.
Quit Terminal and run single instance for vs-mda-remote to resolve this problem if you receive this error for running in Device.
Whether it possible to debug corona SDK application on iOS simulator?
I build a Corona SDK application for Xcode simulator and wrote next commands:
cd /Users/username/Library/Application\ Support/iPhone\ Simulator/7.0.3/Applications/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/app-name.app/
lldb
(lldb) attach --name "app-name" --waitfor
Then I run app in simulator and I get the next message from lldb:
error: attach failed: process did not stop (no such process or permission problem?)
Are you logged in to the Mac remotely (ssh or whatever)? You need to authorize debugging the first time you use the debugger. It's easy to verify if your machine is set up to allow debugging:
% /usr/sbin/DevToolsSecurity -status
Developer mode is currently enabled.
If it's not enabled, I think sudo /usr/sbin/DevToolsSecurity -enable may do the trick. If you're debugging locally, you should see a pop-up window asking you if you want to allow the debugging to happen. But when logged in remotely, you won't see that pop-up of course.