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?
Feb ’25
Reply to Unable to Debug App (Message from debugger: attach failed)
Got it, thanks! I'll look into whether or not I can modify Ableton to allow debugging, and worst-case I can disable SIP temporarily.
Replies
Boosts
Views
Activity
Mar ’25
Reply to Unable to Debug App (Message from debugger: attach failed)
I'm using Ableton Live as the executable. Notably, this error doesn't occur when I am using something local to my project as the executable, like a standalone plugin or the built-in JUCE audio plugin host.
Replies
Boosts
Views
Activity
Mar ’25
Reply to xattr -c not removing com.apple.FinderInfo attribute from Xcode files
Just circling back on this one because I figured out what the problem was; I had my iCloud set to back up my Desktop & Documents, and that was adding the attribute. Every time I removed it, it automatically got added back on because it was trying to upload to iCloud. I stopped uploading desktop & documents, and that solved this issue.
Replies
Boosts
Views
Activity
Mar ’25
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?
Replies
Boosts
Views
Activity
Feb ’25
Reply to xattr -c not removing com.apple.FinderInfo attribute
sorry if this is a repost, I think my original attempt failed to submit because my laptop died right after I clicked 'submit'
Replies
Boosts
Views
Activity
Feb ’25