📦 Deployment Method
Vercel
📌 Version
Latest
💻 Operating System
Windows
📌 System Version
Latest
🌐 Browser
Chrome
📌 Browser Version
Latest
🐛 Bug Description
Gemini模型报错：
{
"error": {
"code": 400,
"message": "Invalid JSON payload received. Unknown name "provider": Cannot bind query parameter. Field 'provider' could not be found in request message.\nInvalid JSON payload received. Unknown name "path": Cannot bind query parameter. Field 'path' could not be found in request message.",
"status": "INVALID_ARGUMENT",
"details": [
{
"@type": "type.googleapis.com/google.rpc.BadRequest",
"fieldViolations": [
{
"description": "Invalid JSON payload received. Unknown name "provider": Cannot bind query parameter. Field 'provider' could not be found in request message."
},
{
"description": "Invalid JSON payload received. Unknown name "path": Cannot bind query parameter. Field 'path' could not be found in request message."
}
]
}
]
}
}
📷 Recurrence Steps
No response
🚦 Expected Behavior
No response
📝 Additional Information
No response
📦 Deployment Method
Vercel
📌 Version
Latest
💻 Operating System
Windows
📌 System Version
Latest
🌐 Browser
Chrome
📌 Browser Version
Latest
🐛 Bug Description
Gemini模型报错：
{
"error": {
"code": 400,
"message": "Invalid JSON payload received. Unknown name "provider": Cannot bind query parameter. Field 'provider' could not be found in request message.\nInvalid JSON payload received. Unknown name "path": Cannot bind query parameter. Field 'path' could not be found in request message.",
"status": "INVALID_ARGUMENT",
"details": [
{
"@type": "type.googleapis.com/google.rpc.BadRequest",
"fieldViolations": [
{
"description": "Invalid JSON payload received. Unknown name "provider": Cannot bind query parameter. Field 'provider' could not be found in request message."
},
{
"description": "Invalid JSON payload received. Unknown name "path": Cannot bind query parameter. Field 'path' could not be found in request message."
}
]
}
]
}
}
📷 Recurrence Steps
No response
🚦 Expected Behavior
No response
📝 Additional Information
No response