I've installed the beta and was able to build a universal app. I haven't tested on an M1 Mac yet, but this bodes well. Thanks a lot.

V4CC beta is available for download:
http://valentina-db.com/download/beta/apple_silicon/v4cc_x64_10_mac.dmg

V4RB is in progress.

V4RB is here:

Hi Ruslan, yes, V4RB. I can't comment on Xojo specifics, but they've made it clear that building for Apple Silicon is in their plans:

Xojo Roadmap

It would be good if Valentina is ready when Xojo adds this capability.

P.S. I assume you have a Xojo license, in which case you can ask to be a beta tester so you're aware of what's coming before it's released.

Hi guys,

any updates to Valentina for Apple Silicon? The new computers are available now and Xojo 2020r2 with Apple Silicon support is in development.

Time to bring this up again. Xojo2020r2 is out and supports ARM builds. I can't build my app, though, because I get this error

"ValentinaPlugin.xojo_plugin:0" does not support macOS arm64

Please update the plugin soon, and I'll upgrade my license.

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 .

And executable has correct permissions, right?

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

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

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.

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

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.

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

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.

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

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

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

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?

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".

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"