[Bug] macOS ARM64 release missing actual binary - snapx-ui wrapper script fails

[Car-Role]

Bug Description

The macOS ARM64 release (SnapX-UI-Release-macOS-0.4.0-alpha.0+g7eafb0f-Arm64.zip) is missing the actual snapx-ui binary. The zip contains a shell script wrapper named snapx-ui (144 bytes) that calls exec env "snapx-ui" "$@", but the real binary it references is not included in the archive.

Steps to Reproduce

1. Download SnapX-UI-Release-macOS-0.4.0-alpha.0+g7eafb0f-Arm64.zip from the v0.4.0 release
2. Unzip it
3. Run ./snapx-ui

Expected Behavior

SnapX launches.

Actual Behavior

env: snapx-ui: No such file or directory

The wrapper script (snapx-ui) is only 144 bytes and contains:

#!/usr/bin/env sh
# SnapX version: 0.4.0-alpha.0+g7eafb0f

dir="$(cd -P -- "$(dirname -- "$0")" && pwd -P)"
cd "$dir"

exec env "snapx-ui" "$@"

The actual binary is not present anywhere in the extracted folder.

Environment

• OS: macOS (Apple Silicon M3)
• Architecture: ARM64
• Release: v0.4.0-alpha.0
• File downloaded: SnapX-UI-Release-macOS-0.4.0-alpha.0+g7eafb0f-Arm64.zip

[BrycensRanch]

Hi, this mistake is unacceptable, and I'll amend it once I get home. I'm ~3 hours away. I was going to point you to the nightly builds but unfortunately, there haven't been any nightlies recently. For the time being, feel free to use this direct link https://github.com/SnapXL/SnapX/actions/runs/24741385817 which should give you a proper archive since this bug was fixed in our development branch already.

[Car-Role]

Hi, this mistake is unacceptable, and I'll amend it once I get home. I'm ~3 hours away. I was going to point you to the nightly builds but unfortunately, there haven't been any nightlies recently. For the time being, feel free to use this direct link https://github.com/SnapXL/SnapX/actions/runs/24741385817 which should give you a proper archive since this bug was fixed in our development branch already.

no worries and no rush on my end! Just thought it would be valuable to make sure you're aware of it. Thanks for maintaining the project!

[philocalyst]

System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
 ---> System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'sysctl' with working directory '/Users/philocalyst'. No such file or directory
   at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo, String, String[], String[], String, Boolean, UInt32, UInt32, UInt32[], Int32&, Int32&, Int32&, Boolean, Boolean) + 0x344
   at System.Diagnostics.Process.StartCore(ProcessStartInfo) + 0x2c4
   at System.Diagnostics.Process.Start(ProcessStartInfo) + 0x3c
   at Aptabase.Core.DeviceDetect.GetMacDeviceModel() + 0x48
   at Aptabase.Core.DeviceDetect.GetDeviceModel() + 0x34
   at Aptabase.Core.SystemInfo..ctor() + 0x38
   at Aptabase.Core.AptabaseClientBase..cctor() + 0x78
   at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0xbc
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0x16c
   at System.Runtime.CompilerServices.ClassConstructorRunner.CheckStaticClassConstructionReturnGCStaticBase(StaticClassConstructionContext*, Object) + 0x14
   at Aptabase.Core.AptabaseClientBase.NewSessionId() + 0x3a8
   at Aptabase.Core.AptabaseClientBase..ctor(String, AptabaseOptions, ILogger) + 0x30
   at Aptabase.Core.AptabaseClient..ctor(String, AptabaseOptions, ILogger`1) + 0x44
   at SnapX.Core.SnapXL.InitTelemetryServices() + 0xcc
   at SnapX.Core.SnapXL.Run() + 0x5f4
   at SnapX.Avalonia.App.OnFrameworkInitializationCompleted() + 0x280

So you know the artifacts there on macos arm don't have .app bundles and error on startup with:

[BrycensRanch]

System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
---> System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'sysctl' with working directory '/Users/philocalyst'. No such file or directory
at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo, String, String[], String[], String, Boolean, UInt32, UInt32, UInt32[], Int32&, Int32&, Int32&, Boolean, Boolean) + 0x344
at System.Diagnostics.Process.StartCore(ProcessStartInfo) + 0x2c4
at System.Diagnostics.Process.Start(ProcessStartInfo) + 0x3c
at Aptabase.Core.DeviceDetect.GetMacDeviceModel() + 0x48
at Aptabase.Core.DeviceDetect.GetDeviceModel() + 0x34
at Aptabase.Core.SystemInfo..ctor() + 0x38
at Aptabase.Core.AptabaseClientBase..cctor() + 0x78
at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0xbc
--- End of inner exception stack trace ---
at System.Runtime.CompilerServices.ClassConstructorRunner.EnsureClassConstructorRun(StaticClassConstructionContext*) + 0x16c
at System.Runtime.CompilerServices.ClassConstructorRunner.CheckStaticClassConstructionReturnGCStaticBase(StaticClassConstructionContext*, Object) + 0x14
at Aptabase.Core.AptabaseClientBase.NewSessionId() + 0x3a8
at Aptabase.Core.AptabaseClientBase..ctor(String, AptabaseOptions, ILogger) + 0x30
at Aptabase.Core.AptabaseClient..ctor(String, AptabaseOptions, ILogger`1) + 0x44
at SnapX.Core.SnapXL.InitTelemetryServices() + 0xcc
at SnapX.Core.SnapXL.Run() + 0x5f4
at SnapX.Avalonia.App.OnFrameworkInitializationCompleted() + 0x280

So you know the artifacts there on macos arm don't have .app bundles and error on startup with:

I am going to have access to an ARM64 MacBook tomorrow to test if I can replicate this. Thanks for the report.