从 Actions SDK 2 迁移到 3:不能在不是使用自定义类别创建的项目中指定自定义操作 [英] Migrating from Actions SDK 2 to 3: Custom actions cannot be specified in projects which are not created using custom category

问题描述

我有一个部署到生产环境(实时)的 Google Action，它是使用旧版本的 Actions SDK 创建的，您在其中拥有操作包，即所谓的第二版 Actions SDK.我的操作不使用 Dialogflow，因此操作控制台中没有迁移按钮或任何内容来执行迁移.

I have a Google Action that is deployed to production (live) and was created with the old version of the Actions SDK where you have the action package, the so called 2nd version of the Actions SDK. My Action doesn't use Dialogflow so there is no migration button or whatsoever in the Actions console to perform a migration.

我尝试过的是使用新的 gactions.exe 并提取当前版本的 Action.刚刚拉动后，我试图将其推回我的 Google Action，但控制台输出显示Actions 项目必须在 actions.yaml 中至少指定一个操作".所以我添加了一个自定义操作，但现在控制台输出显示:

What I have tried is to use the new gactions.exe and just pull the current version of my Action. After just pulling I tried to push it back into my Google Action but the console output said "Actions project must specify at least one action in actions.yaml." So I added a custom action, but now the console output says that:

不能在不是使用自定义类别创建的项目中指定自定义操作."

"Custom actions cannot be specified in projects which are not created using custom category."

我不知道如何解决该问题，因为我认为该错误消息与操作的类别EDUCATION_AND_REFERENCE"无关?

I don't know how to resolve the issue, as I think that that error message isn't related to the Action's category "EDUCATION_AND_REFERENCE"?

非常感谢有关如何解决问题的任何帮助.

Any help is very much appreciated on how to resolve the issue.

推荐答案

好的，我自己想出了如何从未链接到/使用 Dialogflow 项目的旧(遗留)Google Action (v2) 迁移到新的对话操作 (v3).

Ok, I figured out on my own how to migrate from an old (legacy) Google Action (v2) that haven't linked to/used a Dialogflow project to the new Conversational Action (v3).

我单独发布作为指南:指南:如果您的 Action 未连接到 Dialogflow，则从旧的(旧版)Google Action (v2) 迁移到新的 Conversational Action (v3)

这篇关于从 Actions SDK 2 迁移到 3:不能在不是使用自定义类别创建的项目中指定自定义操作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！