chenhg5/cc-connect · error

get file: empty file_path returned for file_id %s

Error message

get file: empty file_path returned for file_id %s

What it means

Returned when getFile succeeds but Telegram returns an empty file_path, which makes constructing a download link impossible. This is a defensive check: without file_path, bot.FileDownloadLink cannot produce a usable URL, so the platform fails fast with the file_id in the message.

Source

Thrown at platform/telegram/telegram.go:1356

	_, err = bot.DeleteMessage(ctx, &tgbot.DeleteMessageParams{ChatID: h.chatID, MessageID: h.messageID})
	if err != nil {
		slog.Debug("telegram: delete preview message failed", "error", err)
	}
	return err
}

func (p *Platform) downloadFile(fileID string) ([]byte, error) {
	bot, err := p.connectedBot("download file")
	if err != nil {
		return nil, err
	}
	ctx := context.Background()
	f, err := bot.GetFile(ctx, &tgbot.GetFileParams{FileID: fileID})
	if err != nil {
		return nil, fmt.Errorf("get file: %w", err)
	}
	if f.FilePath == "" {
		return nil, fmt.Errorf("get file: empty file_path returned for file_id %s", fileID)
	}
	link := bot.FileDownloadLink(f)

	resp, err := p.httpClient.Get(link)
	if err != nil {
		return nil, fmt.Errorf("download file %s: %w", fileID, err)
	}
	defer resp.Body.Close()
	if resp.StatusCode != http.StatusOK {
		return nil, fmt.Errorf("download file %s: status %d", fileID, resp.StatusCode)
	}
	return io.ReadAll(resp.Body)
}

func (p *Platform) ReconstructReplyCtx(sessionKey string) (any, error) {
	// Formats:
	//   telegram:{chatID}                      - shared session, no topic
	//   telegram:{chatID}:{threadID}           - shared session, with topic

View on GitHub (pinned to 4000b2338a)

Solutions

1. Retry the getFile call once — transient empty responses occasionally occur.
2. Verify the bot API client library is current so GetFile responses are parsed into the right fields.
3. Fall back to a different acquisition route (e.g. re-download the media from the originating update).
4. Log the file_id and report it if the problem is reproducible with a specific file.

Example fix

// before
if f.FilePath == "" { return nil, fmt.Errorf(...) }
// after: one retry before failing
if f.FilePath == "" {
    f, err = bot.GetFile(ctx, &tgbot.GetFileParams{FileID: fileID})
    if err == nil && f.FilePath != "" { /* proceed */ }
}

// after GetFile:
if f != nil && f.FilePath == "" { /* treat as retryable */ }

func hasFilePath(f *tgbot.File) bool { return f != nil && f.FilePath != "" }

f, err := bot.GetFile(ctx, &tgbot.GetFileParams{FileID: fileID})
if err != nil { return nil, err }
if f.FilePath == "" {
    // one retry, then fail with file_id in the message
    if f, err = bot.GetFile(ctx, &tgbot.GetFileParams{FileID: fileID}); err != nil || f.FilePath == "" {
        return nil, fmt.Errorf("get file: empty file_path for %s", fileID)
    }
}

When it happens

Trigger: bot.GetFile returns f with f.FilePath == "" — an unexpected/empty API response — and the helper returns this error for the given file_id.

Common situations: Telegram API anomalies or partial responses; certain media types (e.g. some webhook-served files) returning no path; outdated bot API client parsing changes; file recently deleted so the record is incomplete.

Understand the failure class

Background: "empty response", "returned no data", "empty embeddings": what HTTP 200-with-empty-body errors mean across libraries — this error's family across 36 libraries.

Related errors

• get file: %w
• sendVoice failed: %w
• sendAudio fallback failed: %w
• telegram: SendAudio: sendVoice: %w
• telegram: sendWithButtons: %w

AI-assisted analysis of chenhg5/cc-connect@4000b2338a (2026-09-06). Data as JSON: /api/errors/fdb571458cd2dadc. Report an issue: GitHub.