Codesign error: Operation not permitted

Got a LiveCode personal license? Are you a beginner, hobbyist or educator that's new to LiveCode? This forum is the place to go for help getting started. Welcome!

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller

Post Reply
adea
Posts: 12
Joined: Mon Aug 12, 2019 7:44 am

Codesign error: Operation not permitted

Post by adea » Thu Dec 04, 2025 3:59 pm

Hello,

I’m a beginner and currently trying to follow the code-signing steps outlined below.

https://lessons.livecode.com/m/4071/l/1 ... c-appstore

In Step 3 (Codesigning), after replacing the variables, I encountered an “Operation not permitted” error. I’m using an older macOS version, Catalina 10.15.7, and my app was built with LiveCode 9.0.5.

Code: Select all

codesign --deep --force --verify --verbose --timestamp --sign "<your_developer_ID>" --options runtime "<path_to_app_bundle>"
Maynards-MBP:out Adea$ sudo xattr -cr "ITU Sync 2025 v83.app"
Password:
Maynards-MBP:out Adea$ sudo xattr -lr "ITU Sync 2025 v83.app"
Maynards-MBP:out Adea$ sudo chmod -R u+rw "ITU Sync 2025 v83.app"
Maynards-MBP:out Adea$ codesign --deep --force --verify --verbose --sign "Developer ID Application: INTERNATIONAL TELECOMMUNICATION UNION (xxxxxxxxx)" --options runtime "ITU Sync 2025 v83.app"
ITU Sync 2025 v83.app: Operation not permitted

Thank you in advance to anyone who can assist.

kingprince
Posts: 1
Joined: Fri Dec 12, 2025 10:02 am
Contact:

Re: Codesign error: Operation not permitted

Post by kingprince » Fri Dec 12, 2025 10:10 am

That error often happens on Catalina because of permissions. Try moving the app to your Desktop, give Terminal Full Disk Access, then run xattr -cr again before codesigning. That usually clears it up. Also, feel free to visit my site.

adea
Posts: 12
Joined: Mon Aug 12, 2019 7:44 am

Re: Codesign error: Operation not permitted

Post by adea » Mon Dec 22, 2025 6:27 pm

Thank you.
Here is the solution I found:
Click on Apple symbol top left and select "System Preferences"
Open "Security & Privacy"
Select the "Privacy" menu
On the left-hand side, select "Full Disk Access"
on lower left, click the lock and enter your MacOS password or swipe your finger (eyes).
Click the plus button on the right to add Terminal app to the list of things with Full Disk Access. Make sure Terminal is checked when you're done.
reset the lock, and you're done.
shut down Terminal, then restart it.
This should allow Terminal access to the folder in question

Post Reply