模拟器以“语音未被识别”响应。 [英] Simulator responds with "voice not recognized"

问题描述

在Actions Console中使用模拟器时，我得到响应：
由于无法识别您的声音，因此我现在无法执行此操作。请在Google Home应用中检查语音匹配设置。

When using the simulator in the Actions Console, I get the response: "Since your voice wasn’t recognized, I can’t do that right now. Check the Voice Match settings in the Google Home app."

我正在开发的帐户故意没有注册任何设备。该帐户专门用于开发。

The account under which I am developing has no devices registered, intentionally. This account is used specifically and only for development.

模拟器为什么会这样响应，我该如何解决？该帐户没有 Google Home应用。

Why does the simulator respond like this, and how can I fix it? The account has no "Google Home app".

我有另一个（个人）帐户，最初是我用来开发Action的。模拟器在那里可以正常工作。现在，我试图将开发转移到官方公司帐户，并且模拟器完全失败。

I have another (personal) account which I've used to develop the Action initially. The simulator works fine there. Now I'm trying to move the development to an "official" corporate account, and the simulator fails completely.

推荐答案

我可以确认我在这里发生的情况完全相同。
选择使用哪种设备都没有关系。
几天前同样运作良好。
似乎Google已通过帐户关联和Google Simulator上的操作破坏了某些功能。
但是我读过某个地方的最佳实践，您应该提供不需要帐户链接的某些功能。这样，您仍然可以从访问您的助手但拒绝登录的用户那里获得浏览评级。
但这不能解决测试功能的核心问题，该功能要求使用Actions控制台模拟器进行登录。

I can confirm I'm getting exactly the same occurrence here. Doesn't matter what device type is selected as being used. Similarly was working fine a couple of days ago. Looks like Google has broken something with account linking and the Actions on Google Simulator. I did however read somewhere that best practice you should be delivering some functionality that does not require account linking. That way you will still get explore ratings from users who visit your assistant but refuse to sign in. However that doesn't fix the core issue of testing functionality that requires sign-in using Actions console simulator.

这篇关于模拟器以“语音未被识别”响应。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！