[Bug] 第三方api设置后，聊天界面填入key报错key不正确

[XiaolongYang-HZAU]

📦 Environment

Vercel

📌 Version

最新版

💻 Operating System

Windows

🌐 Browser

Edge

🐛 Bug Description

感谢作者提供的优秀工具。在近期更新的几个版本的lobe中，设置了第三方openai api URL后必须在设置界面填入第三方的key才能使用，在聊天页面直接填入key会导致报错‘key不正确或为空’，该bug影响较为严重，希望可以尽快修复。

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @XiaolongYang-HZAU

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[Sen-CaPoo]

有同樣的狀況，更新後用戶設置的 Key 會遺失、新用戶在首次聊天會出現輸入 Key 的提示，但透過聊天室窗內輸入不論輸入甚麼都會失敗，必須至應用設置內去輸入 Key 才會生效。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

In the same situation, the key set by the user will be lost after the update, and a prompt for entering the key for the first chat will be displayed for a new user. However, no matter what is entered through the chat room window, it will fail. You must enter the Key in the application settings to enter the Key. Effective.

[XiaolongYang-HZAU]

该问题在vercel部署的最新版本中似乎仍未得到解决，辛苦团队跟进

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The problem still seems to be unsolved in the latest version of Vercel deployment, thank you for your hard work and the team will follow up

[arvinxx]

经过确认，应该是填完 apikey 后，没有等到落库就点发布请求导致，在 #6112 修复

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

After confirmation, it should be that after filling in the apikey, I clicked to publish the request before I could drop the database. I fixed it in #6112

[lobehubbot]

✅ @XiaolongYang-HZAU

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题，可以留言并回复。

[lobehubbot]

🎉 This issue has been resolved in version 1.53.10 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀