CherryHQ/cherry-studio

[Discussion]: Error details is confusing

Open

#14992 opened on May 11, 2026

View on GitHub
 (0 comments) (1 reaction) (0 assignees)TypeScript (45,688 stars) (4,338 forks)batch import
discussionhelp wanted

Description

Issue Checklist

  • I understand that issues are meant for feedback and problem-solving, not for venting, and I will provide as much detail as possible to help resolve the issue.
  • I have checked the pinned issues and searched through the existing open issues, closed issues, and discussions and did not find a similar suggestion.
  • I confirm that I am here to ask questions and discuss issues, not to report bugs or request features.

Platform

macOS

Version

v1.9.4

Your Question

I'm trying to trouble-shooting API call failed which manually curl on terminal succeeded. This is the error message.

Click "details", I see

The "API Key is invalid, please check and reconfigure" error is not actually not found in response (or anywhere in details page, and manually call the API using curl succeeds so the API key is valid).

And under Request Body Values section, I see

So ... it is using string "[undefined]" as request properties' values? Or are they added to represent valid but unused properties? Having a "request body value" section that does not match the actual request body is confusing, or does it actually pass "[undefined]" as property values?

Context

No response

Additional Information

Priority

Low (Review when available)

Contributor guide

Tech stack
typescript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptReactunderstanding of HTTP error handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the error details modal component, likely located in the frontend codebase. The issue shows that the error message 'API Key is invalid' is displayed incorrectly, and the request body section shows '[undefined]' strings. Check the logic that parses API responses and constructs the error detail view. Look for any hardcoded error messages or incorrect mapping. Consider the possibility that the error message is a fallback when the actual error is not parsed correctly. Also examine how request body values are displayed to ensure they reflect the actual sent payload.