Post

Replies

Boosts

Views

Activity

Reply to xattr -c not removing com.apple.FinderInfo attribute from Xcode files
Thanks for helping out with this! So Xcode is running: codesign --verbose=4 --force --sign - "/Users/julianflack/Desktop/School_Code/DSP/Projects/GRANNY_SMITH/Builds/MacOSX/build/Debug/GRANNY_SMITH.vst3" and in return: /Users/julianflack/Desktop/School_Code/DSP/Projects/GRANNY_SMITH/Builds/MacOSX/build/Debug/GRANNY_SMITH.vst3: resource fork, Finder information, or similar detritus not allowed I tried running the same command in my terminal (replaced --verbose=4 with -vvvvv as suggested), and it gave me the same resource fork error. I then tried your test case with a MyTrue.app situation, and confirmed that com.apple.FinderInfo was causing the error. In the dummy app, I was able to remove the attribute added by SetFile and then the codesign worked fine. However, the attribute in my actual file that's stopping my build still refuses to be removed by any means. One thing I noticed: in the dummy app, the attribute that appeared was 'com.apple.FinderInfo: TEXT', while the attribute showing up in my actual build is just 'com.apple.FinderInfo:'. I'm wondering if that's a clue? I ran xattr -px on it and it returned : 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 As far as where the attribute is getting added, that's tricky because I'm using the JUCE framework as a starting point and not writing the build stuff myself. Any tips on tracking it down?
2w