[Bug]: Cant install on MacBook M1: the default interactive shell is now zsh

[Yaphet2015]

App Version

ComfyUI 0.3.18 - arm64.dmg

Expected Behavior

install on my macbook m1 successfully

Actual Behavior

it stucks here.
And I cant input anything

Steps to Reproduce

install ComfyUI 0.3.18 - arm64.dmg on Macbook M1, MacOS 15.1

P.S. when I ran chsh -s /bin/zsh in my terminal , I got chsh: no changes made and nothing happened.

Debug Logs

cant open

Browser Logs

cant open

Setting JSON

cant open

Other

No response

┆Issue is synchronized with this Notion page by Unito

[robinjhuang]

Hey thanks for reporting this. We've seen some reports of this for mac only. If you run

/Applications/ComfyUI.app/Contents/Resources/uv/macos/uv venv --python 3.12.4

in your terminal, does it do anything?

The terminal when it's shows "Setting up Python environment..." is not interactive. Which terminal did you type chsh -s /bin/zsh into?

[arkalon76]

I have a similar issue, no error message, just stuck, but mine is most likely related to me installing on an external drive that is removed. Uninstall does not seem to resolve it, however, I might not be removing all critical parts.

Running the command above results in:
➜ ~ /Applications/ComfyUI.app/Contents/Resources/uv/macos/uv venv --python 3.12.4 Using CPython 3.12.4 Creating virtual environment at: .venv Activate with: source .venv/bin/activate

[dong4j]

I encountered the same issue, with the latest version being 0.3.30.
I found that bash-3.2$ is the bash version of my root user, which means will comfyui-desktop use the root user's python environment?
But the problem is that I have already set zsh as the default shell, and when starting comfyui-desktop, it used bash instead, resulting in the above warning, and then nothing happened.

I executed /Applications/ComfyUI.app/Contents/Resources/uv/macos/uv venv --python 3.12.4 under the root bash environment:

bash-3.2# /Applications/ComfyUI.app/Contents/Resources/uv/macos/uv venv --python 3.12.4
Using CPython 3.12.4
Creating virtual environment at: .venv
Activate with: source .venv/bin/activate

It seems there are no problem. I see that this issue has been closed, but it's still present in the latest version, I don't know which version will fix this problem?