my Visual Studio 2015 with Xamarin is not recognizing that my android emulator started, it was working just fine in the last days, and it just stopped after I restarted the computer today.
Here is the Output log:
1>Starting deploy API19-Intel_Atom ...
1>Starting emulator API19-Intel_Atom ...
1>C:\Users\Kyore\AppData\Local\Android\ANDROI~1\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd API19-Intel_Atom -prop monodroid.avdname=API19-Intel_Atom
1>Hax is enabled
1>Hax ram_size 0x20000000
1>HAX is working and emulator runs in fast virt mode.
1>emulator: Listening for console connections on port: 5554
1>emulator: Serial number of this emulator (for ADB): emulator-5554
It just get stuck in that line, the emulator starts normally, it is fast and I can open/close things without problems, so I have to press CTRL+BREAK to stop it:
1>Process was cancelled
1>Start emulator API19-Intel_Atom was cancelled.
1>Process was cancelled
Build has been canceled.
I tried to restart the computer, restarted VS, restarted ADB server, decreased emulator RAM and HAXM RAM, it always happen.
Try run Visual Studio with Administrator privilege.
"Run as Administrator"
If that's not working, try
Clear AVD cache, Xamarin cache.
Clean the project right click on solution in VS -> Clean Solution.
Delete bin/obj folders in you project folder manually for e.g.
../MyXamarinProject/bin, ../MyXamarinProject/obj
Create new Android Virtual Device
Related
I've updated Xamarin on Visual Studio 2017 and when I go to build an new Android App I created, it has the following error:
Starting runtime checks
Starting emulator Android_Accelerated_Nougat ...
1>------ Build started: Project: Phoneworld, Configuration: Debug Any CPU ------
C:\Program Files (x86)\Android\android-sdk\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd Android_Accelerated_Nougat -prop monodroid.avdname=Android_Accelerated_Nougat
Could not launch 'C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe': No such file or directory
The selected emulator couldn't be started. This can be caused by the process not having enough permissions. Please try to start VS as administrator, which can help to avoid it.
Emulator Android_Accelerated_Nougat cannot be started.
Runtime checks failed
To run an emulator in normal account that was created as administrator.
2 Steps:
Move 1 folder and 1 .ini file
Change paths values in 2 config files
First, move your emulator's .ini file and folder from admin's account.
Source - C:\Users\{admin account}.android\avd
Destination - C:\Users\{YOUR account}.android\avd
Second, change the emulator paths in 2 config files
Config file 1 - {emulator name}.ini
(1 key-value)
path
Config file 2 - {emulator folder}\hardware-qemu.ini
(4 key-value)
hw.sdCard.path
disk.cachePartition.path
disk.dataPartition.path
disk.encryptionKeyPartition.path
I suggest going doing the following in VS.
Navigate to: Tools > Android > Android SDK Manager and check that you have the correct tools installed for the Nougat android emulator you want to run.
I would say install the following under Android 7.0 - Nougat if not already installed.
Google APIs Intel x86 Atom System Image
Google APIs Intel x86 Atom _64 System Image
Once you have those installed, navigate to: Tools > Android > Android Device Manager.
Select the emulator in question and check what CPU/ABI you target and update it to use the new ones you installed in the previous step.
You should also try running your VS as Administrator, it could also help.
I try to use vscode to debug Expo project.
The expo works fine, setting are as bellow:
Expo XDE: Host: Tunnel
Development Mode
iOS Simulator: Enable Remote Debugging
But when I add Debug in Exponent in VSCode, and click debug,
it will pop up Debug adapter process has terminated unexpectedly without showing any further information.
DEBUG CONSOLE show nothing.
What should I do to finding out what's going on ?
By the way, I didn't see the file ${workspaceRoot}/.vscode/launchReactNative.js
but I have see someone said that this file is not needed.
instead of 'debug in exponent' select 'attach to packager' (but dont click the green arrow yet)
change the packager port (because expo packager defaults to 19001 instead of 19000)) by adding the line "react-native.packager.port": 19001 to user's settings.json
run the app on metro's web ui or by command line (npm run ios/android [or yarn])
click the green arrow to start debuging on vscode
then start the "Remote JS Debugging" on simulator, emulator or device
So this might be a bit of an edge case, but I'm using visual studio on a VM, and I have my phone in my hand. I'd like to set things up that when I press "play" in visual studio, it compiles my cordova app, and pushes it to my phone next to me, so I can test and debug etc.
My phone is 'rooted' and I have installed ADB wifi. I am able to connect to it from Visual Studio's adb version and also adb devices lists it.
(output from cmd.exe running as Admin in the solution folder)
C:\Stuff\Code\svn\myapp\MyApp>adb connect 10.10.10.6
already connected to 10.10.10.6:5555
C:\Stuff\Code\svn\myapp\MyApp>adb devices
List of devices attached
10.10.10.6:5555 device
When I press Play in Visual Studio it compiles and gets to the point where it needs to deploy to the phone and then it comes up with the following error: The system cannot find the file specified
(output from "output" tab in visual studio)
C:/Stuff/Code/svn/myapp/myApp/platforms/android/build/outputs /apk/android-debug.apk
No scripts found for hook "after_build".
No scripts found for hook "after_compile".
------ Copying back to project: android
2>------ Deploy started: Project: MyApp, Configuration: Debug Android ------
2> Querying ADB for attached devices...
2>The system cannot find the file specified
2>The system cannot find the file specified
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
I had a similar issue and this worked for me...
adb kill-server
adb tcpip 5555
adb connect 10.10.10.6
adb devices - should show your device
Open Visual Studio as Admin
Type: ALT+B, R (ALT+B then R) to rebuild your solution
Run your app
I created a Default .net Core RC2 MVC app using VS 2015. I added Docker Support so I could run and debug it in docker.
When I run the project it builds the docker container and starts it. Running the command "docker ps" shows the container running with the correct ports mapped. However I get the following error:
The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use NETStandard [version ...] or newer. This might be expected if the target process did not run.
Also trying to access the web page returns the following error:
[Fiddler] The connection to '10.0.75.2' failed.
Error: ConnectionRefused (0x274d).
System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it 10.0.75.2:80
Turns out the problem is related to the docker for windows beta I am running. By default it does not let you map volumes.
To enable open the docker for window settings:
And select Manage shared drives.
Select the C drive or drive you have the .Net code stored on and rebuild and deploy the project:
I'm trying to set up kernel debugging with VS 2013. When I go to Drivers/Add to add a new target machine, it connects to the remote computer and runs through a lot of setup, but it there are always 2 commands that fail.
I looked up the command that is failing in the log and I pasted it into a batch file and ran it on the target machine. I runs just fine. But then when I try to rerun Add Computer from VS, I get the same failure.
RemoteExecute: Binary: $KitRoot$\Testing\Runtimes\TAEF\te.exe
RemoteExecution: Arguments:
"%SystemDrive%\DriverTest\Run\DriverTestTasks.dll"
/select:"#Name='DriverTestTasks::_ConfigureKernelDebugger'"
/p:"DebugTransport=NET" /p:"NetHost=192.168.1.109" /p:"NetPort=50015"
/p:"NetKey=8XD3HYLMVI0D.RKFEA2BPIXO.27JOLNYURED5.MV9OGRF4XR9V"
/p:"StartPolicy=Active" /p:"IgnoreUserModeExceptions=0"
/p:"SuppressReboot=1"
/rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml
/enableWttLogging
/wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x86)_(possible_reboot)_00007.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0 Initialize: Computer: w8x86wdk-hp
Result completed Test process exit code: -1
I have tried this both with a VMware VM target and against a physical PC target and I have tried adding the computer in the reverse direction and I always get the same failures. I can ping these machines from each other and all machines are Win8 x86. Network discovery and sharing are on. The Windows firewalls are off. These are virgin OS installations so there's nothing on the machines except the OS, VS2013, and WDK 8.1.
Any tips on how to resolve this?
Had same issue when used ws2012 for TARGET machine.
When installed WIN81 instead, turned off UAC and DID NOT install wdk on TARGET - everything started working. Read carefully how to PROVISION TARGET. (it says: dont' install WDK there:)
HOST and TARGET was in the same home workgroup with same passwords for Administrator and MyUserAcc.
also:
under HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System set EnableLUA=0
I am just testing it so I think you should first check your target computer security issue. Then set your port pipe connection and your network adapter setting in your virtual pc.
After that setting make your computer configuration then works perfectly.