blocks|key|407888|text|通过执行以下步骤，我成功地修复了此错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|407889|构建并运行应用程序。|ordered-list-item|407890|在“等待运行时检查”时，构建将停止。|407891|在模拟器中，单击右边工具栏中的>>箭头。|offset|length|style|CODE|407892|记录Windows仿真器内部交换机的IP地址。|BOLD|407893|回到VS。从菜单中选择Tools，→，Android→，Android，ADB命令提示符|407894|adb+connect+[IP_FROM_STEP_#4]型|407895|构建应该继续。|407896|您应该只需要在每次启动模拟器时都这样做。它没有解决VS不自动连接的问题，但我发现这样做很容易，以便继续下去。|407897|另外，如果应用程序运行并立即退出，则执行以下操作：|407898|停止模拟器。|407899|打开Hyper-V+Manager应用程序。|407900|右键单击模拟器并选择“设置”。|407901|展开“处理器”节点并选择“兼容性”。|407902|勾选“迁移到具有不同处理器版本的物理计算机”。|407903|在查看@masound提供的链接之后，我发现注册表项丢失了。所以，我做了以下几件事：|407904|在HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node中添加了"Android工具“键。|unordered-list-item|407905|添加了一个具有名称Path和值C:\Program+Files+(x86)\Android\android-sdk的字符串值。|407906|entityMap^0|0|0|0|F|2|0|2|F|0|0|0|T|0|0|0|0|0|0|0|0|0|0|1|13|0|9|4|F|16|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1J|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1K|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|1L|8|@$I|1M|J|1N|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|1O|8|@$I|1P|J|1Q|K|O]]|9|@]|A|$]]|$1|P|3|Q|5|D|7|1R|8|@]|9|@]|A|$]]|$1|R|3|S|5|D|7|1S|8|@$I|1T|J|1U|K|L]]|9|@]|A|$]]|$1|T|3|U|5|D|7|1V|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1W|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1X|8|@]|9|@]|A|$]]|$1|Z|3|10|5|D|7|1Y|8|@]|9|@]|A|$]]|$1|11|3|12|5|D|7|1Z|8|@]|9|@]|A|$]]|$1|13|3|14|5|D|7|20|8|@]|9|@]|A|$]]|$1|15|3|16|5|D|7|21|8|@]|9|@]|A|$]]|$1|17|3|18|5|D|7|22|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|23|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|1D|7|24|8|@$I|25|J|26|K|L]]|9|@]|A|$]]|$1|1E|3|1F|5|1D|7|27|8|@$I|28|J|29|K|L]|$I|2A|J|2B|K|L]]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|1H|$]]

I managed to fix this error by doing following the below steps: 

<ol>
<li>Build and Run the application .</li>
<li>The build will stall with at "Waiting for Runtime Checks".</li>
<li>In the emulator click the <code>&gt;&gt;</code> arrows in the tool-bar to the right.</li>
<li>Make a note of the IP address for the Windows Phone Emulator Internal Switch.</li>
<li>Back in VS. From the menu select Tools &rarr; Android &rarr; Android ADB Command Prompt </li>
<li>Type <code>adb connect [IP_FROM_STEP_#4]</code>.</li>
<li>The build should continue. </li>
</ol>

You should only need to do this each time the emulator is started. It didn't solve the issue of VS not connecting automatically, but I find it easy enough to do in order to carry on.

As a side note, if the applications runs and immediately quits, then do the following: 

<ol>
<li>Stop the emulator.</li>
<li>Open the Hyper-V Manager application.</li>
<li>Right-click the emulator and select "Settings".</li>
<li>Expand the "Processor" node and select "Compatibility".</li>
<li>Tick "Migrate to physical computer with different processor version".</li>
</ol>

<hr>

After looking at the link provided by @masound I found that the registry key was missing. So, I did the following:

<ul>
<li>Added the "Android SDK Tools" key to <code>HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node</code>.</li>
<li>Added a string value with the name <code>Path</code> and value <code>C:\Program Files (x86)\Android\android-sdk</code>.</li>
</ul>

blocks|key|1645085|text|在这链接中，有一些用于VS+android仿真器的问题。其中之一就是亚行无法连接到模拟器的问题。这是由于仿真程序点的亚行路径与visual所使用的亚行的真实路径之间的差异造成的。此冲突可能是由于更新visual+studio或其组件造成的。简单和永久的解决方案是更改模拟器指向的路径。只需做以下几件事：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1645086|通过从“开始按钮”上下文菜单中选择“运行”、在对话框中键入“regedit”并选择“确定”打开注册表编辑器。|ordered-list-item|1645087|导航到左侧文件夹树中的HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android+SDK工具。|1645088|修改路径注册表变量以匹配Android的路径。|1645089|重新启动模拟器，现在您应该能够看到连接到亚行和相关Android工具的仿真器。|1645090|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/mt228282.aspx^0|1|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$]]|$1|G|3|H|5|F|7|Z|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|10|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|11|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

In <a href="https://msdn.microsoft.com/en-us/library/mt228282.aspx" rel="nofollow noreferrer">this</a> link there are some issue fixings for VS android emulator. One of them is about this problem that adb cannot connect to the emulator. This is caused by the difference between the path of adb that emulator points, and the real path of adb that visual studio works with. This conflicts might be caused by updating visual studio or its components. The simple and permanent solution is to change the path that emulator points to. Just do the followings:

<ol>
<li>Open Registry Editor by selecting Run from the Start buttons context menu, typing regedit in the dialog box, and choosing OK.</li>
<li>Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools in the folder tree on the left.</li>
<li>Modify the Path registry variable to match the path to your Android SDK.</li>
<li>Restart the emulator and you should now be able to see the emulator connected to ADB and associated Android tools.</li>
</ol>

blocks|key|407975|text|卸载仿真器上的应用程序并重新启动模拟器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|407976|这似乎就是为我做的事。我在一个Android+6模拟器上，用HAXM。我还尝试在Use+Shared+Runtime和Use+Fast+Deployment+(debug+mode+only)中禁用xamarin.android+>+properties+>+android+options，这在过去可能有所帮助，但我认为这一次没有帮助。...it还可以重新启动我的电脑七次，然后通过windows+features打开超级电源，然后关机，但谁知道呢。|offset|length|style|CODE|407977|entityMap^0|0|14|I|1N|11|2R|1A|5C|G|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|I|$]]

Uninstall the app on the emulator and restart the emulator.

That seemed to be the thing that did it for me. I was on a Android 6 emulator, with HAXM. I also tried disabling <code>Use Shared Runtime</code> and <code>Use Fast Deployment (debug mode only)</code> in <code>xamarin.android &gt; properties &gt; android options</code> which may have helped in the past but I don't think helped this time. ...it could have also been rebooting my computer seven times and turning hyper-v on and then off through <code>windows features</code> but who knows.

blocks|key|407985|text|我碰到这个了。重新启动了机器和设备。现在一切都好了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|407986|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I ran into this. Rebooted the machine and the device. All good now.

blocks|key|1519969|text|您需要重新启动亚行服务。Visual服务-Android-重新启动亚行服务。这对我有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1519970|在Visual中的菜单栏：Tools+->+Android+->+Restart+Adb+Server|offset|length|style|CODE|1519971|entityMap^0|0|D|12|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

You need restart ADB service. Visual Studio-Service-Android-restart adb service. 
It helped for me.

In Visual Studio from the Menu Bar: <code>Tools -&gt; Android -&gt; Restart Adb Server</code>

blocks|key|408050|text|我也有同样的问题。花了好几个小时来修复它。以上所有的答案都没有结果。打开Android设备管理器，对我的所有仿真器进行工厂重置。它解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|408051|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was having the same issue. Spent hours trying to fix it. Tried all the answers above to no avail. Opened Android Device Manager and did a Factory Reset on all of my emulators. It fixed the problem.

blocks|key|408074|text|因此，在Visual安装自己之前，我使用了另一个Android安装。我还将ANDROID_SDK_ROOT和ANDROID_SDK_HOME环境变量设置到不同的文件夹中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|408075|为了解决这个问题，我首先将ANDROID_SDK_ROOT环境变量更改为使用VS配置的路径(+VS安装了Android，参见Tools+->+Options+->+Xamarin+->+Android+Settings+->+Android+SDK+Location)，在我的例子中，这是C:\Program+Files+(x86)\Android\android-sdk。VS需要在此之后重新启动，因此它加载新的环境变量值。|408076|仅凭这一点还不足以让VS通过亚行成功地连接到AVD。原因是，我的.android路径下的ANDROID_SDK_HOME目录仍然包含以前安装的adbkey和adbkey.pub文件。因此，我将它们替换为VS安装的SDK+(在我的例子中位于C:\Users\<UserName>\.android中)。(删除旧文件可能也足够好，但我还没有对其进行测试。)|408077|之后，VS又能连接到AVD。|408078|entityMap^0|11|G|1I|G|0|D|G|1Q|1Z|40|16|0|W|8|18|G|1Z|6|26|A|3B|S|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1A|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|M|$]]

So in my case, I had another Android SDK installation used, before Visual Studio installed its own. I also had the <code>ANDROID_SDK_ROOT</code> and <code>ANDROID_SDK_HOME</code> environment variables setup to different folders.
To solve the issue, I first changed the <code>ANDROID_SDK_ROOT</code> environment variable to the path that was configured with VS (where the VS installed Android SDK is, see <code>Tools -&gt; Options -&gt; Xamarin -&gt; Android Settings -&gt; Android SDK Location</code>), which was <code>C:\Program Files (x86)\Android\android-sdk</code> in my case. VS needs to be restarted after that, so it loads the new environment variable values.
That alone was not enough to let VS successfully connect to the AVD via ADB. The reason was, that the <code>.android</code> directory under my <code>ANDROID_SDK_HOME</code> path still contained the old <code>adbkey</code> and <code>adbkey.pub</code> files from my previous installation.
I therefore replaced them with the ones from the VS installed SDK (in my case located in <code>C:\Users\&lt;UserName&gt;\.android</code>).
(Just deleting the old files is probably good enough too, but I haven't tested it.)
After that, VS was able to connect to the AVD again.

blocks|key|1520025|text|我和Pixel+2+Pie+8.1(API+27)有同样的问题，我下载了它的高级版本，Pixel+2+Pie+9.0(API+28)，所以它解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1520026|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue with Pixel 2 Pie 8.1(API 27), and I downloaded an upper version of it, Pixel 2 Pie 9.0(API 28), so it has solved the issue.

I have created a new, bare bones, Xamarin Cross Platform application and I get the following error when running the Android project in a VS emulator using Marshmallow (6.0 API 23):

Waiting for runtime checks to complete

The emulator boots up successfully and the project builds without warnings or errors. I've left it in this state overnight, but it fails to get past this point.

<ul>
<li>VS: 15.7.1</li>
<li>Xamarin Forms: 3.0.0.482510</li>
</ul>

Any direction/suggestions would be appreciated. 

EDIT 1: 
Using the Android SDK image works, so the issue seems to be with the Hyper-V VM.

Xamarin "Waiting for runtime checks to complete" and VS Emulator

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我已经创建了一个新的、基本的Xamarin交叉平台应用程序，在VS模拟器中使用Marshmallow (6.0API 23)运行Android项目时，我得到了以下错误：等待运行时检查以完成模拟器成功启动，项目生成时没有警告或错误。我一夜之间就把它留在了这个州，但它没能通过这一点。比较: 15.7.1Xamarin形式:...

问Xamarin“等待运行时检查完成”和VS模拟器
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xamarin“等待运行时检查完成”和VS模拟器EN