Right. As I said, this feature was not added until 2022r1.
…and just to be clear, on macOS this is not something that you add. It’s always there. The reason for this is that on newer OSs even the debug apps have to be at least ad-hoc code-signed, which is what you get if you leave the Developer ID field blank.
FWIW, if all you want is code signing, doing that from the command line is relatively easy. The trick is that any binary code inside the bundle must also be signed and to conform to Apple’s guidelines, they really should be done individually.
Now if you’re going to distribute your app to other users, you’ll also need to Notarize. Apple made that easier recently, but if you’re going to go through all this, you should seriously consider @Sam_Rowlands App Wrapper. He’s taken all the guesswork out and even makes it easy to automate.
Well all I need is that my program runs on my clients iMac. I have built my program and I copied the file to his program folder and it runs on his iMac. I am doing it myself with anydesk.
But it sends out corrupt, zero bytes pdf files.
So I started the game: find the error. It works on my computer.
Maybe it is a ‘signing the program’ -error?
Although like Greg said the code signing is always there.
I will start with buying the MonkeyBread xojo plugin so that I can sent mails with a pdf.
If it still sends out zero sized pdf files, I will know that it isn’t the program which fails.
Then I will buy the App Wrapper and code-sign the program.
If all that fails I will hire a proffessional…
Thank you all for answering, especially on a saturday.
Just to be clear, trusting that things will work everywhere just because they work on your machine is going to hurt you in the long run. Ad-hoc signatures only work on your machine and the other issues you are running into sound like they may be caused by the app expecting to find a resource that only exists on your machine and nowhere else. You should have at least one other machine or virtual machine that you do testing on that is not your build machine. Ideally, one for each OS & Version that you support. For instance, I have an M1 MacBook Pro for development and run macOS 12 & 13 in parallels on that machine as well as Windows 11 ARM and a 2018 Mac Mini with parallels which has macOS 10.13.6 through 13.2, Windows 7, 8, 8.1, 10 and 11, as well as several different flavors & versions of Linux. All just for testing purposes. All of which have a plain vanilla snapshot so I can get back to a known state quickly.
Well that is a professional setup. I am new to xojo but i have been a programmer for more than 25 years. And copy and past an exe to a computer of a client never worked on windows. But I tried it with my xojo program this morning, and it seems to be working. Well it didn’t give any errors.
Thank you all for your help.
Ps, it works on my computer is one of the lines I have read somewhere meant as a funny statement.
Would this apply to compiled Applescripts used within the app? I’m having errors every time I try to sign an app using the steps in the XOJO docs. Mind you, the signing is failing with a basic ‘hello world’ app so I doubt the Applescripts are the issue - but if they may be an issue down the track I’d prefer to know…