langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Uncaught Error: Minified React error #130; visit #13571

New Issue
Closed
opened 2026-02-21 19:12:48 -05:00 by yindo · 7 comments
yindo commented 2026-02-21 19:12:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @dashing9527 on GitHub (Apr 30, 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.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

normal

❌ Actual Behavior

This is a workflow. An error occurred just a few seconds after editing it

Originally created by @dashing9527 on GitHub (Apr 30, 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.3.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/637e56cd-f821-4511-94b1-06ca6fbe3699) ### ✔️ Expected Behavior normal ### ❌ Actual Behavior This is a workflow. An error occurred just a few seconds after editing it
yindo added the 🤔 cant-reproduce label 2026-02-21 19:12:48 -05:00
yindo closed this issue 2026-02-21 19:12:48 -05:00
yindo commented 2026-02-21 19:12:48 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (Apr 30, 2025):

The problems caused by the upgrade are normal in version 1.2

@dashing9527 commented on GitHub (Apr 30, 2025): The problems caused by the upgrade are normal in version 1.2
yindo commented 2026-02-21 19:12:48 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 30, 2025):

Please provide some information about the browser's infomation.

@crazywoola commented on GitHub (Apr 30, 2025): Please provide some information about the browser's infomation.
yindo commented 2026-02-21 19:12:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 30, 2025):

I found two similar discussions related to client-side exceptions in Dify:

  1. Application error: a client-side exception has occurred (see the browser console for more information) - This discussion is still open and was last updated on February 27, 2025 [1].

  2. When entering the editing agent or app page, an error occurs: "Application error: a client-side exception has occurred (see the browser console for more information)" - This discussion is also open and was last updated on February 20, 2025 [2].

Regarding React error #130, it typically occurs due to issues with component rendering or state management in React applications. Since you mentioned warnings about non-passive event listeners and forced reflow violations, these could be contributing factors. These issues might be related to changes made in the upgrade from version 1.2 to 1.3.1, as you noted that the problems were normal in version 1.2.

To address this, you might want to check the browser console for more detailed error messages and trace the stack to identify the source of the error. Additionally, reviewing any changes made to the React components during the upgrade could help pinpoint the cause.

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 (Apr 30, 2025): <!-- Answer --> I found two similar discussions related to client-side exceptions in Dify: 1. [Application error: a client-side exception has occurred (see the browser console for more information)](https://github.com/langgenius/dify/discussions/14294) - This discussion is still open and was last updated on February 27, 2025 <sup>[[1]](https://github.com/langgenius/dify/discussions/14294)</sup>. 2. [When entering the editing agent or app page, an error occurs: "Application error: a client-side exception has occurred (see the browser console for more information)"](https://github.com/langgenius/dify/discussions/14076) - This discussion is also open and was last updated on February 20, 2025 <sup>[[2]](https://github.com/langgenius/dify/discussions/14076)</sup>. Regarding React error #130, it typically occurs due to issues with component rendering or state management in React applications. Since you mentioned warnings about non-passive event listeners and forced reflow violations, these could be contributing factors. These issues might be related to changes made in the upgrade from version 1.2 to 1.3.1, as you noted that the problems were normal in version 1.2. To address this, you might want to check the browser console for more detailed error messages and trace the stack to identify the source of the error. Additionally, reviewing any changes made to the React components during the upgrade could help pinpoint the cause. <!-- 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/2df511fb-f305-484f-bd33-1220616f69f0?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/2df511fb-f305-484f-bd33-1220616f69f0?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/2df511fb-f305-484f-bd33-1220616f69f0?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/2df511fb-f305-484f-bd33-1220616f69f0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2df511fb-f305-484f-bd33-1220616f69f0?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/2df511fb-f305-484f-bd33-1220616f69f0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2df511fb-f305-484f-bd33-1220616f69f0?feedback_type=other)</sup>
yindo commented 2026-02-21 19:12:49 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (Apr 30, 2025):

请提供有关浏览器信息的一些信息。

@crazywoola I'm using the edge browser. After switching the browser, it still has errors. Below is the location of the debug error. I don't know if you can spot any problems. Not all ChatFlows are wrong.

Image

@dashing9527 commented on GitHub (Apr 30, 2025): > 请提供有关浏览器信息的一些信息。 @crazywoola I'm using the edge browser. After switching the browser, it still has errors. Below is the location of the debug error. I don't know if you can spot any problems. Not all ChatFlows are wrong. ![Image](https://github.com/user-attachments/assets/81c7269b-0c73-40ed-b225-f098b3203114)
yindo commented 2026-02-21 19:12:49 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 30, 2025):

See duplicated with https://github.com/langgenius/dify/issues/19128.

What's your edge version?

@crazywoola commented on GitHub (Apr 30, 2025): See duplicated with https://github.com/langgenius/dify/issues/19128. What's your edge version?
yindo commented 2026-02-21 19:12:49 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (Apr 30, 2025):

参见 duplicated with #19128。

您的边缘版本是什么？

@crazywoola 135.0.3179.98 But it should have nothing to do with edge. The same result occurred when I used Google chrome

@dashing9527 commented on GitHub (Apr 30, 2025): > 参见 [duplicated with #19128](https://github.com/langgenius/dify/issues/19128)。 > > 您的边缘版本是什么？ @crazywoola 135.0.3179.98 But it should have nothing to do with edge. The same result occurred when I used Google chrome
yindo commented 2026-02-21 19:12:49 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (May 5, 2025):

I pulled the code of the main branch again today, and it's working fine now...

@dashing9527 commented on GitHub (May 5, 2025): I pulled the code of the main branch again today, and it's working fine now...
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 🤔 cant-reproduce
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#13571
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?