Application error: a client-side exception has occurred (see the browser console for more information).

[fniu]

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.13.1

Cloud or Self Hosted

Cloud

Steps to reproduce

A simple workflow to call an LLM.

✔️ Expected Behavior

Run normally.

❌ Actual Behavior

Application error: a client-side exception has occurred (see the browser console for more information).

[dosubot]

I found a similar unsolved discussion regarding a client-side exception in the Dify repository. You can view it here ^[1].

Regarding the issue you're experiencing, it seems to be related to Content Security Policy (CSP) violations and a TypeError involving the _dfy_model_identity property. Dify handles CSP by setting a CSP header in the middleware, which includes a whitelist of domains. This can be configured using the NEXT_PUBLIC_CSP_WHITELIST environment variable in production. The necessary domains for CSP include Google Analytics-related domains ^[2].

The TypeError you're encountering, which involves reading properties of null, might be due to attempting to access a property on an object that is not properly initialized or is null. This is a common cause of TypeError in the Dify codebase ^[3].

To address these issues, you might want to:

1. Check the CSP configuration to ensure that all necessary domains are included in the whitelist.
2. Investigate the initialization of objects related to _dfy_model_identity to ensure they are not null before accessing their properties.

These steps could help resolve the client-side exceptions you're facing.

To continue talking to Dosu, mention @dosu.

---

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

[Ellioben]

SAME Bug! How to Fix it? bro😀😀

[crazywoola]

Can you provide the reproduceable steps?

[fniu]

I think it has something to do with the (optional) input field. I have an example (attached yml DSL) that reproduce the error. In this example, the error is gone, if you remove the optional input from workflow or make sure the optional input is not empty.

You can try with any text as the input and leave the optional input empty.

app_error.txt

[crazywoola]

I think it has something to do with the (optional) input field. I have an example (attached yml DSL) that reproduce the error. In this example, the error is gone, if you remove the optional input from workflow or make sure the optional input is not empty.

You can try with any text as the input and leave the optional input empty.

app_error.txt

I tried both empty and not empty, still can not reproduce this error.
·

[jpgsns]

Same thing here when i try to see the outputs of a Model step.

[correlli]

I only experience this when I open the trace log of Extractin Parameter block.
It says client-side but does it so?

[JzoNgKVO]

Fixed in #11432

[correlli]

Still, I get this error only for the Extracting Parameter block.

[JzoNgKVO]

Still, I get this error only for the Extracting Parameter block.

Today's new release will include PR #11438 . The new version has not been released yet.