larksuite / larksuite/cli

vc +meeting-join (bot 入会) 报 code 10012 "gray release scope",如何开通该能力?

Open
#1,788 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug domain/vc
Dominant language
Go
Stars
17.3k
Forks
1.4k
Avg merge
2d 4h
Merged PRs (30d)
105

Description

问题描述

vc +meeting-join 让机器人(应用/bot 身份)加入会议时,报 code 10012,提示会议 owner 不在 gray release scope 内。想确认这是应用可用范围(开发者后台可自助设置)问题,还是飞书官方对该能力的灰度白名单(需申请开通)问题,以及正确的开通方式。

环境
  • lark-cli 版本:1.0.64
  • 身份:--as bot
复现步骤

三个相关 scope 均已在开发者后台申请并通过(调用不再报 app_scope_not_applied):

  • vc:meeting.bot.join:write
  • vc:meeting.meetingevent:read
  • vc:meeting.message:write

执行:

lark-cli vc +meeting-join --as bot --meeting-number <9位真实会议号>
实际结果
{
  "ok": false,
  "identity": "bot",
  "error": {
    "type": "api",
    "subtype": "unknown",
    "code": 10012,
    "message": "The meeting owner is not included in the gray release scope, so joining the meeting via application identity is not allowed."
  }
}
  • log_id(最近一次):20260708101730FCCD7CFB09E9CEFC1ACC
  • 调用前有一行日志:[Error] [apply app_ticket, response error: msg:app resend fail,code:10016](不确定是否相关)
疑问
  1. 这里的 gray release scope 到底指什么?是应用的可用范围/可见范围(开发者后台可自助设置),还是飞书官方对「机器人应用身份入会」这个能力的灰度白名单
  2. 如果是能力灰度:自建应用如何申请开通?有没有自助入口,还是必须提工单 / 找企业商务?审批周期大概多久?
  3. 能否在 vc +meeting-join 的文档 / help 里补充这个能力的开通前置说明,避免使用者 scope 都配好了却卡在灰度、无从下手?
期望

明确 code 10012 的开通路径,并在文档中补充前置条件说明。

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the vc +meeting-join command and its documentation or help text, then verify how error code 10012 and the gray release scope are described. Confirm the official activation path and whether the app scopes listed in the issue are sufficient; done means the prerequisite and opening process are documented clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.