Xojo does take independent plugin dylibs for intel and arm code and joins them for universal builds.
And then signing is required, which Xojo seems to do with adhoc signatures.
I do not have full data of those. I was just opening this discussion to at first at least verify that the Joining was supposed to be working as intended.
Re-reading the post from the customer then he can build either x64 build or Apple Silicon that uses EHAES.dylib from e-CryptIt Engine, but if he builds universal then it skips the Apple Silicon segment, thus fails to join as far as I can tell from the info I have.
As far as I can tell from the report then it skips joining, he lists some logs that show Xojo Internet Encodings having both arcs and same with rbframework.dylib but the one from my plugin showing only x86_64 in the universal build.
The library there is about 2x the size of each so its definitely joining for me. My question is a bit on the randomness, where it seems only some are getting strangeness’s like this, same with signing I guess.
User of course might have much more in his project that somehow messes up in the compile
I can try to get more data, and see if the customer can reproduce it in simple example App that he can send us, which I could then forward. So we are not sending you guys on wild goose chase having no good test case.