Hi @TBC I cannot reproduce this I am afraid. But I have an idea. Can you check the executable status on both your *aarch64.app package and the file you use inside that package as well? If they are both executable, that is fine. If one of them is not executable (I presume the one inside the package is), then can you make whichever is not, executable. By default they should be executable, but I guess an erroneous chmod could cause something like this.
If that is no help, is there anything else you can tell us about this? For example, what happens when you do try and run the app package? Is there an error you are given?
