[X] I have searched the opened issues and there are no duplicates
Describe the bug
When packaging via flet build macos -vv, build files seem to be generated in the directories like /var/folders/q1/dcc1rnq13f9fhs4hxd03jqy80000gn/T/flet_flutter_build_* and /var/folders/q1/dcc1rnq13f9fhs4hxd03jqy80000gn/T/serious_python_temp*. If the build fails, the serious_python_temp files seem to linger potentially taking up a significant amount of space and not indicating to the user in any way that this exists and needs to be deleted manually.
Code sample
Happens with any app, though naturally this is a bigger problem with larger apps. In my case, I was debugging packaging issues so trying many builds and my serious_python_temp* directory quickly ballooned to > 80GB
Duplicate Check
Describe the bug
When packaging via
flet build macos -vv
, build files seem to be generated in the directories like/var/folders/q1/dcc1rnq13f9fhs4hxd03jqy80000gn/T/flet_flutter_build_*
and/var/folders/q1/dcc1rnq13f9fhs4hxd03jqy80000gn/T/serious_python_temp*
. If the build fails, theserious_python_temp
files seem to linger potentially taking up a significant amount of space and not indicating to the user in any way that this exists and needs to be deleted manually.Code sample
Happens with any app, though naturally this is a bigger problem with larger apps. In my case, I was debugging packaging issues so trying many builds and my serious_python_temp* directory quickly ballooned to > 80GB
To reproduce
Run
flet build macos
on an app that will fail to build. I ran into this issue while tracing down https://github.com/flet-dev/flet/issues/4007 which is trivially reproducible.Expected behavior
No response
Screenshots / Videos
No response
Operating System
macOS
Operating system details
M1 Pro Sequioa 15.0 (also repro'd on Sonoma 14.5)
Flet version
0.24.1
Regression
I'm not sure / I don't know
Suggestions
No response
Logs
Additional details
No response