[NET 6.0] Can osx-arm64 be published under a Windows x64 machine?

[sn4k3]

I need clarification on this title subject.

On my machine (Windows 11 x64) i publish multiple packages of my app, now with net6.0 one of them is osx-arm64. But users are not able to run it without call dotnet appname.dll. In my attempts i ask an mac M1 user to publish the app from code in his machine, and it work right away by double clicking the binary.

Compile command is as follow: dotnet publish $project -o "publish" -c Release -r osx-arm64 -p:PublishReadyToRun=true --self-contained

My question is as title, it's possible to use a x64 machine to make the compilation for arm64? Or that's the cause of my problem?

Issue source: sn4k3/UVtools#431 (comment)

[vitek-karas]

This is probably due to signing. M1 macOS requires all executables to be signed. When the app is built on macOS the SDK will call the signing tool to "Fake sign it", so that it works at least locally. When the app is built anywhere else, the singing tool is not available (and fake signing may not work anyway).

[sn4k3]

@shmellyorc Looks like your app is x64? Does it work with a native arm bundle? My problem is with native arm (osx-arm64) build. x64 runs fine even without any chmod.

I see you use p:TieredCompilation does it make any diference on this senario?

[shmellyorc]

@shmellyorc Looks like your app is x64? Does it work with a native arm bundle? My problem is with native arm (osx-arm64) build. x64 runs fine even without any chmod.

I see you use p:TieredCompilation does it make any diference on this senario?

Reason why I use p:TieredCompilation is because of Monogame framework. It is required so it doesn't stutter. Outside of Monogame, a normal dotnet core 6 arm-x64 console app, I don't know :(.

Pretty much I built this on my PC not mac so I had to bundle it myself but my build process is:
dotnet publish -c Release -r osx-x64 /p:PublishReadyToRun=false /p:TieredCompilation=false --self-contained

[sn4k3]

I also bundled everything on PC WSL, as said, the osx-x64 works on both x64 and arm64(emulated), but osx-arm64 dont work with macOS arm64 when it come from web download.
I haven't try codesign yet because i own no apple developer account, but most likely is the solution.

My script: https://github.com/sn4k3/UVtools/blob/master/build/createRelease.sh

[agocke]

Notarization is stricter for ARM64 than for x64. Given that Apple has been escalating notarization requirements in most of its OS updates, on both x64 and ARM64, it's possible that a future update will stop your app from working without notarization on x64 as well.

[shmellyorc]

Notarization is stricter for ARM64 than for x64. Given that Apple has been escalating notarization requirements in most of its OS updates, on both x64 and ARM64, it's possible that a future update will stop your app from working without notarization on x64 as well.

Well.. Mac going to lose a bunch of customers than. I know Mac is trying to make themselves appear "exclusive" with the ARM64 but it'll be a cost of their doing. exclusivity == no competition == more money

All I do is make games so I don't need to worry about signing since Steam covers the code signing. Feel sorry for the people making apps outside of steam as majority of your expenses are from Code Signing. I know from code signing, you are paying a massive chunk of money for the app being certified and pretty much saying "its a good app". I cannot support code signing because, to me, feels like a monopoly.

Pretty much: "Get code signed or your app wont work here any more." What happened being creative and designing new cool apps to make peoples lives better? I know many developers don't finish their app because the massive amount of cash required for code signing or other certificates.

Kind of sad... but I hope you release your awesome apps.

-shmelly