1. Jonathan Ashwell
  2. Valentina Database ADK
  3. Montag, Januar 17 2022, 05:17 PM
  4.  Abonnieren via E-Mail
Using Xojo plugin 11.4.3 in Monterey -> no problem. But when I try to run in Monterey I get a Valentina runtime error, and upgrading to the current Valentina release doesn't fix it. I've uploaded a screen snap of the error.
Anhänge
Kommentar
There are no comments made yet.
Sergey Pashkov Akzeptierte Antwort
Hello Jonathan,

What versions of Monterey and Xojo are used?
Kommentar
There are no comments made yet.
Jonathan Ashwell Akzeptierte Antwort
The most recent versions of each:

Monterey 12.1

Xojo 2021R3.1
Kommentar
There are no comments made yet.
Sergey Pashkov Akzeptierte Antwort
Do you have a code signing in this app?
If yes - the following thread suggests disabling library validation or re-signing the dependent libraries.
Referenzen
  1. https://developer.apple.com/forums/thread/126895
Kommentar
There are no comments made yet.
Jonathan Ashwell Akzeptierte Antwort
Hm, I already resign all Valentina libraries as part of the codesigning process.
Kommentar
There are no comments made yet.
Sergey Pashkov Akzeptierte Antwort
During this process - do you call install vcomponents script that copies libraries to the app bundle?
As shown on the screenshot with this error the plugin tries to load libraries from /usr/local/lib/vcomponents_x64.
Kommentar
There are no comments made yet.
Jonathan Ashwell Akzeptierte Antwort
I see my first post had a nasty type. Signing works in Mojave, fails in Monterey.

Yes, I call the install script provided provided by Paradigmasoft. And the dylibs are in /usr/local/lib

If I turn off codesigning the app just crashes on launch.

The part of the report that seems the most interesting is "libvshared_fat_release_x64.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs)". I'm not sure what the Team ID refers to, though.

I googled this and found a post from @Beatrix Willius# another crash involving signing of

vcomponents_x64/libvshared_fat_release_x64.dylib

but that was in High Sierra (which my app compiled fine in), so may not be related at all.

crash post

Maybe Beatrix will get in on this conversation.
Anhänge
Kommentar
There are no comments made yet.
Jonathan Ashwell Akzeptierte Antwort
Solved - I updated the XCode command line tools in Terminal:

xcode-select --install

and no longer get the error.

Thanks for pointing me towards codesigning as the culprit, it helped me track this down.
Kommentar
There are no comments made yet.
  • Seite :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.