Gemini version 0.8 plug-in, output json_schema format, all have the ```json logo, and the previous version 0.5 did not have this problem #149

Closed
opened 2026-02-16 10:18:14 -05:00 by yindo · 3 comments
Owner

Originally created by @jasoncym on GitHub (Mar 29, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Gemini version 0.8 plug-in, output json_schema format, all have the ```json logo, and the previous version 0.5 did not have this problem

Now only if you restore to version 0.5, you can use it normally. This problem is quite large and directly affects the workflow that requires json output.

✔️ Expected Behavior

I hope this kind of json output should not change at will. It is best to stabilize it. There are also updated models. Can they be pulled in real time? This time I originally wanted a new 2.5pro model, but unfortunately I haven't seen it yet.

Actual Behavior

json_schema has been set, and when output, there is still a ```json identifier

Originally created by @jasoncym on GitHub (Mar 29, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Gemini version 0.8 plug-in, output json_schema format, all have the ```json logo, and the previous version 0.5 did not have this problem Now only if you restore to version 0.5, you can use it normally. This problem is quite large and directly affects the workflow that requires json output. ### ✔️ Expected Behavior I hope this kind of json output should not change at will. It is best to stabilize it. There are also updated models. Can they be pulled in real time? This time I originally wanted a new 2.5pro model, but unfortunately I haven't seen it yet. ### ❌ Actual Behavior json_schema has been set, and when output, there is still a ```json identifier
yindo closed this issue 2026-02-16 10:18:14 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Mar 29, 2025):

Hey @jasoncym! 👋 I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's squash those bugs together!

The issue you're experiencing with the json_schema output format in Gemini version 0.8, where the output includes the ```json identifier, seems to be a change from the previous version 0.5. Unfortunately, I couldn't find specific details about this change in the repository or documentation.

To address this, you might consider using JSON Schema to customize and stabilize the JSON output format. By defining a JSON Schema structure, you can ensure that the output strictly adheres to the defined data structure, potentially avoiding unexpected changes like the inclusion of the ```json identifier. You can enable JSON Schema in the settings and switch the response_format column to json_schema format to control the output format [1][2].

Regarding accessing new models like the 2.5pro, I couldn't find specific steps in the repository. It might be worth checking if there are any updates or configurations available in the platform settings that allow you to access the latest models.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 29, 2025): <!-- Greeting --> Hey @jasoncym! 👋 I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's squash those bugs together! <!-- Answer --> The issue you're experiencing with the `json_schema` output format in Gemini version 0.8, where the output includes the ```json identifier, seems to be a change from the previous version 0.5. Unfortunately, I couldn't find specific details about this change in the repository or documentation. To address this, you might consider using JSON Schema to customize and stabilize the JSON output format. By defining a JSON Schema structure, you can ensure that the output strictly adheres to the defined data structure, potentially avoiding unexpected changes like the inclusion of the ```json identifier. You can enable JSON Schema in the settings and switch the `response_format` column to `json_schema` format to control the output format <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/jp/learn-more/extended-reading/how-to-use-json-schema-in-dify.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/jp/learn-more/how-to-use-json-schema-in-dify.md)</sup>. Regarding accessing new models like the 2.5pro, I couldn't find specific steps in the repository. It might be worth checking if there are any updates or configurations available in the platform settings that allow you to access the latest models. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/be408724-bbfa-4953-b3f0-49bab9f50e10?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/be408724-bbfa-4953-b3f0-49bab9f50e10?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/be408724-bbfa-4953-b3f0-49bab9f50e10?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/be408724-bbfa-4953-b3f0-49bab9f50e10?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/be408724-bbfa-4953-b3f0-49bab9f50e10?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/be408724-bbfa-4953-b3f0-49bab9f50e10?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/be408724-bbfa-4953-b3f0-49bab9f50e10?feedback_type=other)</sup>
Author
Owner

@ct-03 commented on GitHub (Apr 1, 2025):

I already enable json schema, then i encounter another problem:

[google] Error: PluginInvokeError: {"args":{},"error_type":"AttributeError","message":"'NoneType' object has no attribute 'upper'"}

Gemini plugin version 0.1.1
Selfhost system

@ct-03 commented on GitHub (Apr 1, 2025): I already enable json schema, then i encounter another problem: ``` [google] Error: PluginInvokeError: {"args":{},"error_type":"AttributeError","message":"'NoneType' object has no attribute 'upper'"} ``` **Gemini plugin version 0.1.1** **Selfhost system**
Author
Owner

@dosubot[bot] commented on GitHub (Aug 18, 2025):

Hi, @jasoncym. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that Gemini plugin version 0.8 outputs JSON schema with a ```json code block identifier, unlike version 0.5, which disrupts workflows requiring clean JSON.
  • I suggested using JSON Schema settings to stabilize output formatting but noted a lack of clear documentation on this change or how to access newer models like 2.5pro.
  • Another user mentioned an AttributeError when enabling JSON schema on Gemini plugin version 0.1.1 in a self-hosted environment, possibly related.
  • The issue remains unresolved with no clear fix or documentation update provided yet.

What's Next:

  • Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If I don’t hear back within 5 days, this issue will be automatically closed to keep the backlog manageable.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 18, 2025): Hi, @jasoncym. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that Gemini plugin version 0.8 outputs JSON schema with a ```json code block identifier, unlike version 0.5, which disrupts workflows requiring clean JSON. - I suggested using JSON Schema settings to stabilize output formatting but noted a lack of clear documentation on this change or how to access newer models like 2.5pro. - Another user mentioned an AttributeError when enabling JSON schema on Gemini plugin version 0.1.1 in a self-hosted environment, possibly related. - The issue remains unresolved with no clear fix or documentation update provided yet. **What's Next:** - Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If I don’t hear back within 5 days, this issue will be automatically closed to keep the backlog manageable. Thanks for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#149