You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tools: name custom app packages so they survive a release upload
create-app-{linux,macos,windows}.sh named their output after APP_NAME
verbatim. For any app whose name has a space, GitHub rewrites the space
to a dot when the file is uploaded as a release asset, so what CI
produces and what users download are two different file names.
That silently broke the Linux launcher: create-app-linux.sh writes a
.sh next to the AppImage that execs it by name, so every published
launcher pointed at a file that does not exist under that name. Four
sat-mtl apps ship one today, all dead:
exec "$SCRIPT_DIR/Spatial Protocol Mapper-linux-x86_64.AppImage"
# asset is actually Spatial.Protocol.Mapper-linux-x86_64.AppImage
Use APP_NAME_SAFE for the file names, which create-app.sh already
derives and create-app-wasm.sh already uses. APP_NAME still names the
app itself: the .desktop entry, the DMG volume, the window title.
Also make --qml absolute the way --score and --local-installer already
are. The platform scripts cd into their work directory before copying,
so a relative --qml resolved to nothing there and the copy is guarded
with `|| true` -- the app was packaged with an empty qml directory and
no error. Only reachable from the command line: the package-custom-app
action passes absolute paths already.
Verified by packaging a wasm bundle with a relative --qml and a name
with spaces: the qml now arrives, and the output is
Spatial-Protocol-Mapper-wasm.zip.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VxtUwsfk4JN46WropbwfqC
0 commit comments