豆豆友情提示:这是一个非官方 GitHub 代理镜像,主要用于网络测试或访问加速。请勿在此进行登录、注册或处理任何敏感信息。进行这些操作请务必访问官方网站 github.com。 Raw 内容也通过此代理提供。
Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Address Copilot comment: adjust error example
  • Loading branch information
JKirsch1 committed Apr 16, 2026
commit 75bd6ce13e0ed6bb2fefa8308a4ee036d2489d1e
10 changes: 1 addition & 9 deletions docs/quickstart/includes/publish-errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,16 +8,8 @@ The error message typically indicates the source of the problem.

For example, suppose the identifier `Contoso.App.Logger.Test` exists on nuget.org. If you try to publish a package with that identifier, you get the following error:

```output
Response status code does not indicate success: 409 (A package with ID 'Contoso.App.Logger.Test' and version '1.0.0' already exists and cannot be modified.).
```

To address this problem, increment the version, rebuild the project, re-create the *.nupkg* file, and retry the `push` command.

If you use an expired or invalid API key when you run the `push` command, you get the following error:

```output
Response status code does not indicate success: 403 (The specified API key is invalid, has expired, or does not have permission to access the specified package.).
```

If you get this error, check the scope, expiration date, and value of your API key.
To address this situation, check the scope, expiration date, and value of your API key. If the key is valid, the error indicates that the package identifier already exists on the host. To overcome the problem, change the package identifier to be unique, rebuild the project, re-create the *.nupkg* file, and retry the `push` command.