Did some more testing with the most simple method of debugging using messageboxes:

// LOCAL MODE:

if( gClient = false ) then

  Valentina.Init( mCacheSize )

  

  if Valentina.CacheSize = 0 then

    MsgBox "Valentina was not initialized!"

  end if

end if 



MessageBox "Will init Valentina"



// CLIENT MODE

if (gClient = true) then

  Valentina.Init(100 * 1024 * 1024, "", "")

  Valentina.YieldMode = False

end if



Messagebox "Valentina inited"



// -------------------------------------

// Set debug level for Valentina plugin logs.

Valentina.DebugLevel = EVDebugLevel.kLogParams



MessageBox "Log params set"

I get the messageboxes "Will init Valentina" and "Valentina inited". I don't get "Log params set".

I'm not officially out of ideas. I built again. Did a codesign and notarised the app. It starts fine and then it crashes. I don't have sudo access to this computer.

@Jonathan Ashwell: do you have a link to your app as ARM version?

I'm an idiot. I needed to codesign the subfolder:

/Users/beatrixwillius/Desktop/My\ http://Application.app/Contents/Frameworks/vcomponents_x64/*

I thought I'd try again. But even with the new script I still get an error on codesign.

/usr/bin/codesign --timestamp -f -s 'Developer ID Application: Beatrix Willius (72695Z3887)' /Users/beatrixwillius/Desktop/My\ Application.app/Contents/Frameworks/*
/Users/beatrixwillius/Desktop/My Application.app/Contents/Frameworks/SQLiteDatabase.dylib: replacing existing signature
/Users/beatrixwillius/Desktop/My Application.app/Contents/Frameworks/XojoFramework.framework: replacing existing signature
/Users/beatrixwillius/Desktop/My Application.app/Contents/Frameworks/v4rb_cocoa_64.dylib: replacing existing signature
/Users/beatrixwillius/Desktop/My Application.app/Contents/Frameworks/vcomponents_x64: bundle format unrecognized, invalid, or unsuitable

To follow up -- I built as a Universal and sent it to someone with an M1 Mac...he reports there are no obvious problems. So for me at least (using the V4RB ADK) all seems to be well. Thanks for your work on this.

Is it possible to try to run the Valentina Server on the DTK? To know if the problem is V4RB-related or Valentina ARM build just doesn't work.

I uploaded the installer.
Also, I uploaded the server in a zip archive, running it from some home folder shows a log in the terminal:
vserver_universal/vserver_x64.app/Contents/MacOS/vserver_x64

Built the app again and did the codesign manually. It starts fine on a DTK and crashes without crash log when starting to use Valentina. There is no information in the Console. I tried to start the app with Terminal "open app". But there is no information.

Here's the script. In my tests, codesign works with this structure

Looks like codesign doesn't work when a bundle has non-standard structure.

Some time ago we made changes to place vcomponents and vresources to the standard paths

app/Contents/Frameworks/vcomponents_64
app/Contents/Resources/vresources

install_vcomponents_v4rb doesn't reflect these changes, I'll update it soon.

I'm trying to do codesign manually because Xojo doesn't do post-build scripts for the universal app. But I get an error when codesigning vcomponents:

beatrixwillius@Beatrixs-MacBook-Air ~ % /usr/bin/codesign --timestamp -f -s 'Developer ID Application: Beatrix Willius (72695Z3887)' /Users/beatrixwillius/Desktop/My\ http://Application.app/Contents/vcomponents_x64/*
/Users/beatrixwillius/Desktop/My http://Application.app/Contents/vcomponents_x64/libvclient_fat_release_x64.dylib: replacing existing signature
/Users/beatrixwillius/Desktop/My http://Application.app/Contents/vcomponents_x64/libvkernel_fat_release_x64.dylib: replacing existing signature
/Users/beatrixwillius/Desktop/My http://Application.app/Contents/vcomponents_x64/libvshared_fat_release_x64.dylib: replacing existing signature
/Users/beatrixwillius/Desktop/My http://Application.app/Contents/vcomponents_x64/vresources: bundle format unrecognized, invalid, or unsuitable

No, we don't have the hardware yet.

But I can't run it even on Catalina, exactly the same message was shown.

Changing the quarantine attribute helped:
xattr -dr com.apple.quarantine My\ Application.app

The app isn't codesigned. I should see the "your app could be malicious" if codesign was a problem.

Do you have hardware to test? Here is the link to the app: http://www.mothsoftware.com/downloads/myapp.zip .

We don't use symlinks, but it is worth to check the code signature like it is said in the article:

codesign -vvvv "MyApplication.app"

What are the permissions on the executable?

ls -l "http://MyApplication.app/Contents/MacOS/"

Also, it is possible to check the permissions for all files in the bundle, e.g.:

ls -Rl "My Application.app" > permissions_report.txt

Maybe open command in the terminal can show the error?

open "MyApplication.app"

Could this be relevant problem (not the Safari but the symlink part)?

https://furbo.org/2020/12/01/codesign-the-saga-continues/

I built as usual, uploaded to my ftp and downloaded the app because I'm testing at the DTK of a friend. I did some testing for the Chilkat plugin last week or so and was able to start my app on the computer.

And executable has correct permissions, right?

I just got the 5th email from the forum software with the same content.

There is no message in Console. Can't start the app in Terminal "permission denied".

Hello Beatrix,

What if you open the Console.app - are there any log entries for the time when the application was started?
What if you start the application from the Terminal.app, e.g:

user$  "...http://MyApplication.app/Contents/MacOS/MyApplication"

Is there any error message?

Did the building on my MacBook Air with BS, latest Valentina and latest Xojo beta. I picked an example at random. Not a full app build.

App starts fine on BS and on High Sierra. On a DTK I get "App is damaged and can't be opened." I tried both a zip file and a dmg. I executed the "install_vcomponents" script after the complete build was finished with Terminal.