"PhpStorm does not have write access to /Applications/PhpStorm.app/Contents"
I am unable to update PHPStorm due to the above error message. However, if I navigate to that folder and check permissions, they look fine.
请先登录再写评论。
From your second screenshot, I see that the app is owned by the `admin` user, and the permissions for other users are `r-x`, which means they don't have write access to the file.
I suspect that you're using a different user account (not `admin`) to run and update PhpStorm.
Please open the Terminal, run `sudo chown -R $(whoami) /Applications/PhpStorm.app/`. This will change the ownership of the PhpStorm application files to your user.
Then try to update the PhpStorm again.
That doesn't work in macOS 26.4.1 (25E253). Shouldn't writes to files in /Applications/[bundle].app happen only during Application updates? Changing a file named .zsh_sessions seems like a change in preferences or settings. Shouldn't this be happening in ~/Library/Application Support/com.jetbrains.phpstorm/… or ~/Library/Preferesnces/.com.jetbrains.phpstorm/[something]…?
If I move the app to ~/Applications that solves it because that is not as highly a privileged directory as /Applications and I am the owner of all items in ~/Applications.
We haven't been able to reliably reproduce this error on macOS 26.4.1 on our side yet. We tested the default setup (download the binaries from site, install it on behalf the current user), if you know, what you do differently, please let us know.
That said, to clarify: PhpStorm does not write settings or preferences into the app bundle. All user data is stored under ~/Library/Application Support/JetBrains/PhpStorm/, exactly as you'd expect on macOS. The only time PhpStorm needs write access to /Applications/PhpStorm.app/Contents is during self-updates, when the IDE patches its own binaries. If the app bundle isn't writable at that point, you'll see this error.
Regarding .zsh_sessions: that's managed by macOS itself (stored at ~/.zsh_sessions/), not something PhpStorm writes to.
Workaround (will work despite most of probable issue causes): use JetBrains Toolbox for managed updates