The fact that the solution is hard to find with only the error message made me decide to write a blog post about it anyway. Click checkbox “Migrate to a physical computer with a different processor version”Īnd of course, once you know that, you can find people have encountered this problem before, like here in the MSDN forums, on Stackoverflow or even here in comments on the release notes of the emulator.Select the emulator you are trying to use.The solution to that takes the following steps, which are even less obvious: Not an obvious thing to do, but hey, that’s almost nothing in our field. That will usually take care of the issue. Go to the properties of the Android project, hit tab “Android options”, and unselect “Use Fast Deployment” The first error – the missing, which is usually hidden in a plethora of messages - is easy to fix: disable Android fast deployment. The issue is solely the debugger not being able to connect. Oddly enough, when you start the deployed app on the emulator by clicking on it, it runs fine. This actually even happens when you do File/New Project and run, which is very frustrating. You get one or more of the following messages in your output window:ĪOT module '' not found: dlopen failed: library "/data/app/.Droid-1/lib/x86/" not found.This kept me puzzled for a while, and only with the combined help of my fellow MVPs Mayur Tendelkar and Tom Verhoeff, who both had pieces of the puzzle, I was able to finally get this working.Īs you try to deploy an app to the Visual Studio Android emulator, symptoms are as follows: While I was busy developing a cross-platform application for Windows Phone, Android and iOS I wanted to test the Android implementation and ran into a snare – I could no longer debug on the emulator. Fix for “could not connect to the debugger” while deploying Xamarin Forms apps to the Visual Studio Android Emulator
0 kommentar(er)
