langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

com.fasterxml.jackson.core.JsonParseException: #7141

New Issue
Closed
opened 2026-02-21 18:19:07 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 18:19:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @mdxlCJ on GitHub (Dec 11, 2024).

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

0.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Request dify with parameter a, specific value R: 111, or token, value is: EAA25127B638EBE05A4D35561F7CF2FE， Then, dify this parameter and request the HTTP POST server again, but an error occurs, Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'EAA25127B638EBE05A4D35561F7CF2FE': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')

✔️ Expected Behavior

Can you receive all parameters

❌ Actual Behavior

Partial business cannot be implemented

Originally created by @mdxlCJ on GitHub (Dec 11, 2024). ### 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 0.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Request dify with parameter a, specific value R: 111, or token, value is: EAA25127B638EBE05A4D35561F7CF2FE， Then, dify this parameter and request the HTTP POST server again, but an error occurs, Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'EAA25127B638EBE05A4D35561F7CF2FE': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') ### ✔️ Expected Behavior Can you receive all parameters ### ❌ Actual Behavior Partial business cannot be implemented
yindo added the 🐞 bug label 2026-02-21 18:19:07 -05:00
yindo closed this issue 2026-02-21 18:19:07 -05:00
yindo commented 2026-02-21 18:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 11, 2024):

The error you're encountering, com.fasterxml.jackson.core.JsonParseException, suggests that the token EAA25127B638EBE05A4D35561F7CF2FE is not being recognized as a valid JSON value. This typically happens when the input is not properly formatted as a JSON string, number, array, object, or one of the JSON literals (null, true, false).

To resolve this issue, ensure that the token is correctly formatted in the JSON request. If EAA25127B638EBE05A4D35561F7CF2FE is meant to be a string, it should be enclosed in double quotes, like this:

{
  "token": "EAA25127B638EBE05A4D35561F7CF2FE"
}

Make sure that all JSON keys and string values are enclosed in double quotes and that the JSON structure is valid. This should help in avoiding the JsonParseException. If the issue persists, double-check the entire JSON payload for any other formatting errors.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Dec 11, 2024): <!-- Answer --> The error you're encountering, `com.fasterxml.jackson.core.JsonParseException`, suggests that the token `EAA25127B638EBE05A4D35561F7CF2FE` is not being recognized as a valid JSON value. This typically happens when the input is not properly formatted as a JSON string, number, array, object, or one of the JSON literals (`null`, `true`, `false`). To resolve this issue, ensure that the token is correctly formatted in the JSON request. If `EAA25127B638EBE05A4D35561F7CF2FE` is meant to be a string, it should be enclosed in double quotes, like this: ```json { "token": "EAA25127B638EBE05A4D35561F7CF2FE" } ``` Make sure that all JSON keys and string values are enclosed in double quotes and that the JSON structure is valid. This should help in avoiding the `JsonParseException`. If the issue persists, double-check the entire JSON payload for any other formatting errors. <!-- 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/460b9022-9d44-49cd-91f3-190cee0ff994?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/460b9022-9d44-49cd-91f3-190cee0ff994?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/460b9022-9d44-49cd-91f3-190cee0ff994?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/460b9022-9d44-49cd-91f3-190cee0ff994?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/460b9022-9d44-49cd-91f3-190cee0ff994?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/460b9022-9d44-49cd-91f3-190cee0ff994?feedback_type=other)</sup>
yindo commented 2026-02-21 18:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 11, 2024):

Please upgrade to latest version.

@crazywoola commented on GitHub (Dec 11, 2024): Please upgrade to latest version.
yindo commented 2026-02-21 18:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@mdxlCJ commented on GitHub (Dec 12, 2024):

dify 上 http 请求 ，json解析错误，先不要给我closed
WechatIMG95

@mdxlCJ commented on GitHub (Dec 12, 2024): dify 上 http 请求 ，json解析错误，先不要给我closed <img width="643" alt="WechatIMG95" src="https://github.com/user-attachments/assets/cee3494c-628a-450a-91df-0cb058455ac7" />
yindo commented 2026-02-21 18:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 12, 2024):

image image
@crazywoola commented on GitHub (Dec 12, 2024): <img width="773" alt="image" src="https://github.com/user-attachments/assets/aa535152-8a1b-4e2e-b255-edeac0d28442" /> <img width="593" alt="image" src="https://github.com/user-attachments/assets/f6e6ad39-f26b-4266-b7c4-65fefacccb61" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7141
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?