Repository navigation
[Question]Windows: Packaged Flet app creates a separate "Flet description" taskbar window #6767
QuestionBug: Packaged Flet app creates a separate "Flet description" taskbar window on WindowsHello Flet team, I am experiencing a Windows desktop packaging issue with my Flet application. After packaging my Python + Flet application into an EXE and running it, the application itself works normally. However, Windows Taskbar shows an additional application/window entry called: "Flet description" When I right-click the application icon on the Windows Taskbar, there is a separate entry for "Flet description". If I click on that entry, Windows opens another completely separate blank white window. This blank window is not part of my Python/Flet application. The problem is that when I close my main application, this additional "Flet description" window/process remains open and I have to close it separately. Expected behaviorI expect the packaged application to behave as a single Windows application:
Actual behaviorAfter packaging:
EnvironmentOS: Python: Flet: Packaging method: For example: Flet version can be obtained with: pip show flet Python version: python --version ImportantI have already tried several approaches to solve this problem, including:
None of these approaches resolved the issue. The problem appears to be related to the Flet Windows desktop runtime / Flutter client / taskbar process association rather than my application UI code. I have attached screenshots showing the behavior. Could you please help me identify:
Hello Flet team, I have a Windows Flet application packaged as an EXE. After running the packaged application, Windows shows an additional Taskbar entry called "Flet description". Clicking it opens a separate blank white window that is completely independent from my main application. When I close my main application, this extra window remains open and must be closed separately. I have already tried all the suggested solutions, including:
Unfortunately, none of these solutions fixed the problem. I believe this may be related to the Flet Windows runtime / Taskbar process handling. Could you please help me identify the correct solution? I can provide screenshots, my Flet version, Python version, and packaging command if needed. Thank you. Code sampleNo response Error messageNo response ------------------------------------------------------
|
Replies: 1 comment
|
|


flet builddoesnt have an issue - i tested it to confirm.But
flet packdoes, and I am just from opening a PR to address it: #6793