search

packagesdev / packages

Integrated Packaging Environment for OS X
312 stars 44 forks source link

Installed plugin doesn't retain its file type and shows up as a folder instead on M1 Mac #116

Open beyhanklc opened 2 years ago

beyhanklc commented 2 years ago

The installed plugin doesn't retain its file type and shows up as a folder instead. I am seeing this on all plugin formats, VST, VST3, AU, AAX plugins. You can see the below image, the created folder is forbidden and it says:

The folder “MyPlugin.component” can’t be opened because you don’t have permission to see its contents

Same installer that was built on Intel Mac Catalina, works on M1 Mac. But if that installer is built on on M1 Mac Mini and also M1 MacBook Pro (Monterey & BigSur), I am getting below result on the same system.

plggg

packagesdev commented 2 years ago

I would suggest to check the POSIX permissions in the Terminal and in the payload of the project. And also compare the working .pkg to the not working .pkg using Pacifist.

beyhanklc commented 2 years ago

Thank you for the suggestions. Ok I made some tests. After adjusting the POSIX permissions, apparently that fixed the issue. Just for checking, is it ok to give all permissions for this case like below?

Not working version

before

Working version

after

packagesdev commented 2 years ago

Others should not have Write permission => drwxrwxr-x

brinsche-fkt42 commented 2 years ago

I have the same problem with an .app payload, Finder just displays this icon Bildschirmfoto 2022-05-18 um 15 35 13 and the app can't be opened.

But I have the same problem no matter whether I build on an M1 Mac or an Intel Mac.

Edit: I just recreated the problem with a new .pkgproj with this app https://dl.nwjs.io/v0.64.1/nwjs-v0.64.1-osx-x64.zip which my app is based on in case that is helpful Also, if I chown the app afterwards as my own user it works again, but doing that in postinstall seems like a really hacky workaround

Edit2: Nevermind, I think my problem is caused a permission problem inside the nwjs.app itself, not by packages.