mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
[Bug] The vertex_ai plugin version 0.0.27 has a bug in the "Parameter Extractor" function, causing an error when calling it. #804
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CarGod on GitHub (Nov 13, 2025).
Self Checks
Dify version
1.9.0
Plugin version
0.0.27
Cloud or Self Hosted
Cloud
Steps to reproduce
The LLM node is functioning normally, but selecting a Gemini-related model in the "parameter extractor" causes an error
✔️ Error log
[vertex_ai] Error: req_id: f3fed0ba4a PluginInvokeError: {"args":{"description":"[models] Error: 'NoneType' object has no attribute 'get'"},"error_type":"InvokeError","message":"[models] Error: 'NoneType' object has no attribute 'get'"}
@dosubot[bot] commented on GitHub (Nov 13, 2025):
Hi @CarGod! I'm Dosu and I’m helping the dify-official-plugins team.
This is a known issue with the vertex_ai plugin when using Gemini models in certain workflows like the Parameter Extractor. The error
'NoneType' object has no attribute 'get'happens because the plugin expects a specific response format from Vertex AI, but Gemini models sometimes returnNoneor a malformed response—often due to using the:predictendpoint instead of the required:streamGenerateContentendpoint for Gemini. This leads to the plugin trying to access.geton aNonevalue, which isn't handled defensively in the current codebase. This issue is specific to Gemini models and does not affect all models or nodes (for example, the LLM node works as expected) [source].Workarounds reported by users include: using supported regions like
us-central1, switching to non-preview Gemini models, retrying requests if errors are intermittent, or using Gemini 2.5 flash-lite for more stability. Also, double-check that your Vertex AI credentials and region are correctly configured—setting region toglobalis not supported for embeddings and can cause issues [source].A migration to the new
google-genaiSDK with improved response handling and defensive checks has been implemented in a recent pull request, but it may not be available in your current plugin version (0.0.27). Monitoring for plugin updates or applying the above workarounds is recommended until a full fix is released [source].To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@nadazero commented on GitHub (Nov 19, 2025):
@Zhaohuai-L please have a look at this issue and fix this bug ASAP please, this issue will block testing new model such as gemini 3.0
@Zhaohuai-L commented on GitHub (Nov 20, 2025):
@nadazero Thanks for pointing out this issue. I'll try to reproduce and fix it locally. BTW, I've already added gemini3 with signature support locally. I'll get the PR up for this soon.
@Zhaohuai-L commented on GitHub (Nov 21, 2025):
@nadazero This issue has been fixed in https://github.com/langgenius/dify-official-plugins/pull/2111
@nadazero commented on GitHub (Nov 21, 2025):
Thank you very much!
@dosubot[bot] commented on GitHub (Dec 7, 2025):
Hi, @CarGod. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!