The problem stems from MacOS associating signature information with the vnode, and it isn't recomputed if the file already exists, leading to a cryptic error if you upgrade tailwind and overwrite the binary.
The solution is to first delete the file, which seems to force recomputation of the signature since a new inode/vnode is created when you download the file again.
It's not the cleanest thing, but without this upgrading tailwind on MacOS leads to super cryptic errors.
chrismccord
commented
1 year ago
This closes https://github.com/phoenixframework/tailwind/issues/39
The problem stems from MacOS associating signature information with the vnode, and it isn't recomputed if the file already exists, leading to a cryptic error if you upgrade tailwind and overwrite the binary.
The solution is to first delete the file, which seems to force recomputation of the signature since a new inode/vnode is created when you download the file again.
It's not the cleanest thing, but without this upgrading tailwind on MacOS leads to super cryptic errors.
More color on the issue here: https://stackoverflow.com/questions/67378106/mac-m1-cping-binary-over-another-results-in-crash