I do see this as a problem. If you use an App Wrapper script, it will intervene and sign the debug build (and remove all what it knows that can cause this error), however in my testing, the App Wrapper script is called after Xojo attempts to sign the ARM build.
Perhaps @Greg_O_Lone and I could work together to create a solution whereby Xojo doesn’t attempt this if App Wrapper is going to be doing it for you?
App Wrapper has supported website distribution since it became a requirement from Apple.
In App Wrapper 4, you can switch between Website and App Store easier thanks to the GUI redesign. Alternatively you can do this from a Xojo IDE script, meaning a project constant can control how your application gets wrapped.
In the summer of 2019, I started to redesign App Wrapper so that the processing engine was much faster, for cases just like this. When you use App Wrapper, you’re getting a full analysis of your app and preparation for code signing. The engine is not only quicker than using the terminal command, it is even more thorough (signing executables that the terminal command may miss).
Different apps have different requirements for code signing, there is no one-size fits all, and a lot to be learned (plenty of which is not documented by Apple).
The apostrophe ’ and plus symbols (+) in your app’s name would be worrying to me, since that could be triggering a build script error due to improper quoting. Does it work if you rename your app from CheckPrint’R+