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

Icon setting does not work correctly. #21776

New Issue
Open
opened 2026-02-21 20:14:15 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:14:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @sysailab1112-svg on GitHub (Jan 19, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Step 1. Create Agent

Image

Step 2. Run the Agent

Image

Step 3. Chat page

Image

✔️ Expected Behavior

The chat icon should be like the setting.

❌ Actual Behavior

The chat icon does not be like the setting.

Originally created by @sysailab1112-svg on GitHub (Jan 19, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce # Step 1. Create Agent <img width="1920" height="953" alt="Image" src="https://github.com/user-attachments/assets/79b4af4e-d64f-41f5-bbd9-5698cfbcc33f" /> # Step 2. Run the Agent <img width="1920" height="953" alt="Image" src="https://github.com/user-attachments/assets/3052ced8-dc5a-4617-aea6-13595a1d2a2b" /> # Step 3. Chat page <img width="1920" height="953" alt="Image" src="https://github.com/user-attachments/assets/0b2147d5-8297-4116-9974-a14dd8a36ff7" /> ### ✔️ Expected Behavior The chat icon should be like the setting. ### ❌ Actual Behavior The chat icon does not be like the setting.
yindo added the 🐞 bugstale labels 2026-02-21 20:14:15 -05:00
yindo commented 2026-02-21 20:14:15 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 19, 2026):

Hi @sysailab1112-svg! I'm Dosu and I’m helping the dify team.

This is a known issue in Dify self-hosted (Docker) setups: the chat icon sometimes does not match the icon set in the agent/app settings due to a combination of frontend caching, state management, and static asset handling. The icon in the chat UI is rendered from data provided by the backend and cached in the frontend; if the cache is not invalidated or the backend does not provide the updated icon, the UI will not reflect changes. This problem is often made worse by Nginx misconfiguration or aggressive static asset caching, which can prevent new icons from being served or displayed correctly example.

To troubleshoot: clear your browser cache, check your Nginx config to ensure static assets are served with no-cache or a short max-age, and verify your Docker volume mappings for static files. If you use a subpath or reverse proxy, make sure your frontend build sets the correct basePath and that Nginx rewrites paths properly. If the issue persists, rebuilding your Docker image and redeploying can help. Also, check the browser console/network for failed icon requests or 404s example.

This bug has been confirmed in multiple versions and is pending a robust fix, but many improvements have been made in recent releases. Upgrading to the latest Dify version is recommended for persistent icon display issues example.

If you need more technical detail or want to dig into the code, the chat icon is rendered by the AppIcon component, which receives its data from the useChatWithHistory hook and React-query cache. Icon updates depend on the app metadata being refreshed from the backend; if the cache is stale, the UI won't update example.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 19, 2026): <!-- Greeting --> Hi @sysailab1112-svg! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known issue in Dify self-hosted (Docker) setups: the chat icon sometimes does not match the icon set in the agent/app settings due to a combination of frontend caching, state management, and static asset handling. The icon in the chat UI is rendered from data provided by the backend and cached in the frontend; if the cache is not invalidated or the backend does not provide the updated icon, the UI will not reflect changes. This problem is often made worse by Nginx misconfiguration or aggressive static asset caching, which can prevent new icons from being served or displayed correctly [example](https://github.com/langgenius/dify/issues/23928). To troubleshoot: clear your browser cache, check your Nginx config to ensure static assets are served with `no-cache` or a short `max-age`, and verify your Docker volume mappings for static files. If you use a subpath or reverse proxy, make sure your frontend build sets the correct `basePath` and that Nginx rewrites paths properly. If the issue persists, rebuilding your Docker image and redeploying can help. Also, check the browser console/network for failed icon requests or 404s [example](https://github.com/langgenius/dify/issues/29708). This bug has been confirmed in multiple versions and is pending a robust fix, but many improvements have been made in recent releases. Upgrading to the latest Dify version is recommended for persistent icon display issues [example](https://github.com/langgenius/dify/issues/26332). If you need more technical detail or want to dig into the code, the chat icon is rendered by the `AppIcon` component, which receives its data from the `useChatWithHistory` hook and React-query cache. Icon updates depend on the app metadata being refreshed from the backend; if the cache is stale, the UI won't update [example](https://github.com/langgenius/dify/blob/cb51a449d3696c9356a816b026ca68e1c47462cf/web/app/components/base/chat/chat-with-history/hooks.tsx#L73-L604). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/b62251bc-d0f5-4b29-807e-23a10c9fc77d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b62251bc-d0f5-4b29-807e-23a10c9fc77d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b62251bc-d0f5-4b29-807e-23a10c9fc77d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b62251bc-d0f5-4b29-807e-23a10c9fc77d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b62251bc-d0f5-4b29-807e-23a10c9fc77d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b62251bc-d0f5-4b29-807e-23a10c9fc77d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b62251bc-d0f5-4b29-807e-23a10c9fc77d?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20in%20Dify%20self-hosted%20%28Docker%29%20setups%3A%20the%20chat%20icon%20sometimes%20does%20not%20match%20the%20icon%20set%20in%20the%20agent/app%20settings%20due%20to%20a%20combination%20of%20frontend%20caching%2C%20state%20management%2C%20and%20static%20asset%20handling.%20The%20icon%20in%20the%20chat%20UI%20is%20rendered%20from%20data%20provided%20by%20the%20backend%20and%20cached%20in%20the%20frontend%3B%20if%20the%20cache%20is%20not%20invalidated%20or%20the%20backend%20does%20not%20provide%20the%20updated%20icon%2C%20the%20UI%20will%20not%20reflect%20changes.%20This%20problem%20is%20often%20made%20worse%20by%20Nginx%20misconfiguration%20or%20aggressive%20static%20asset%20caching%2C%20which%20can%20prevent%20new%20icons%20from%20being%20served%20or%20displayed%20correctly%C2%A0%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/23928%29.%0A%0ATo%20troubleshoot%3A%20clear%20your%20browser%20cache%2C%20check%20your%20Nginx%20config%20to%20ensure%20static%20assets%20are%20served%20with%20%60no-cache%60%20or%20a%20short%20%60max-age%60%2C%20and%20verify%20your%20Docker%20volume%20mappings%20for%20static%20files.%20If%20you%20use%20a%20subpath%20or%20reverse%20proxy%2C%20make%20sure%20your%20frontend%20build%20sets%20the%20correct%20%60basePath%60%20and%20that%20Nginx%20rewrites%20paths%20properly.%20If%20the%20issue%20persists%2C%20rebuilding%20your%20Docker%20image%20and%20redeploying%20can%20help.%20Also%2C%20check%20the%20browser%20console/network%20for%20failed%20icon%20requests%20or%20404s%C2%A0%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/29708%29.%0A%0AThis%20bug%20has%20been%20confirmed%20in%20multiple%20versions%20and%20is%20pending%20a%20robust%20fix%2C%20but%20many%20improvements%20have%20been%20made%20in%20recent%20releases.%20Upgrading%20to%20the%20latest%20Dify%20version%20is%20recommended%20for%20persistent%20icon%20display%20issues%C2%A0%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/26332%29.%0A%0AIf%20you%20need%20more%20technical%20detail%20or%20want%20to%20dig%20into%20the%20code%2C%20the%20chat%20icon%20is%20rendered%20by%20the%20%60AppIcon%60%20component%2C%20which%20receives%20its%20data%20from%20the%20%60useChatWithHistory%60%20hook%20and%20React-query%20cache.%20Icon%20updates%20depend%20on%20the%20app%20metadata%20being%20refreshed%20from%20the%20backend%3B%20if%20the%20cache%20is%20stale%2C%20the%20UI%20won%27t%20update%C2%A0%5Bexample%5D%28https%3A//github.com/langgenius/dify/blob/cb51a449d3696c9356a816b026ca68e1c47462cf/web/app/components/base/chat/chat-with-history/hooks.tsx%23L73-L604%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31249)
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 stale 🐞 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#21776
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?