[Bug] azure 服务商配置不正常

[ysicing]

📦 Environment

Docker

📌 Version

v1.45.5

💻 Operating System

macOS

🌐 Browser

Edge

🐛 Bug Description

同样的配置老版本是没问题的，新版本

看日志

Route: [azure] InvalidProviderAPIKey: { error: undefined, errorType: 'InvalidProviderAPIKey' }
Route: [azure] InvalidProviderAPIKey: { error: undefined, errorType: 'InvalidProviderAPIKey' }
Route: [azure] InvalidProviderAPIKey: { error: undefined, errorType: 'InvalidProviderAPIKey' }
 ⨯ ReferenceError: Cannot access 'm' before initialization
    at Object.y (.next/server/chunks/39817.js:257:19183)
    at <unknown> (.next/server/chunks/39817.js:257:23459)
    at <unknown> (.next/server/chunks/86177.js:159:1345)
    at o (.next/server/chunks/86177.js:159:1740)
    at s (.next/server/chunks/86177.js:159:1766)
    at d (.next/server/chunks/86177.js:159:1943)
    at <unknown> (.next/server/chunks/39817.js:257:23405)
    at t.a (.next/server/webpack-runtime.js:1:989)
    at 955225 (.next/server/chunks/39817.js:257:23158)
    at t (.next/server/webpack-runtime.js:1:143) {
  digest: '2116735162'
}
Route: [azure] InvalidProviderAPIKey: { error: undefined, errorType: 'InvalidProviderAPIKey' }
Route: [azure] InvalidProviderAPIKey: { error: undefined, errorType: 'InvalidProviderAPIKey' }

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @ysicing

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。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot]

Hey @ysicing! I'm here to help you squash those bugs, answer your questions, and guide you to becoming a contributor. Let's tackle this together! 🤖

The "InvalidProviderAPIKey" error you're encountering with the Azure service configuration in version v1.45.5 could be due to a missing or incorrect API key or endpoint during the instantiation of the LobeAzureOpenAI class. This error is thrown when the API key or endpoint is not provided ^[1].

Additionally, the "ReferenceError: Cannot access 'm' before initialization" suggests there might be an issue in the code where a variable is being used before it has been properly initialized. Unfortunately, there is no specific documentation or comments in the code that explain this error ^[2].

To address the "InvalidProviderAPIKey" error, ensure that the API key and endpoint are correctly configured and provided. If the issue persists, it might be related to a known problem where valid credentials are incorrectly flagged as invalid, and a future update may be required to resolve this ^[2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[lobehubbot]

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

---

Yes, I have updated two versions, but it is still not resolved.

[ysicing]

@arvinxx have any good troubleshooting methods or suggestions to solve this problem?

[arvinxx]

I will look into it today

[lobehubbot]

✅ @ysicing

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

[lobehubbot]

🎉 This issue has been resolved in version 1.46.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀