I have an issue when I tried to export a bot
It happened when I changed the path of export to desktop.
I didn’t see what was the original path to test it.
Could you please confirm whether that part was working prior to version 8.3.213?
no same issue, I reinstall version 8.3.212. Same error
Hi,
New issue: the standalone export fails (RTILA 8.3.213, macOS 26.6.1, Apple
Silicon arm64). Export destination: Desktop — not the cause, the failure
happens during packaging, before any file is created.
Error:
Building
Packaging bot archive...
Build Error
Could not locate the RTILA engine binary. Could not locate rtila-engine
sidecar in resources.
I ran read-only checks on my machine — everything about the binary itself is
healthy:
-
The engine IS present at the standard sidecar location, next to the other
sidecars:/Applications/RTILA.app/Contents/MacOS/rtila-engine
(alongside rtila-x, rtila-database, rtila-relay, rtila-cloudflared)-rwxr-xr-x, 91,721,872 bytes, Mach-O 64-bit executable arm64 — correct
architecture, executable bit set, no quarantine attribute -
/Applications/RTILA.app/Contents/Resources contains only icon.icns,
rtila-extension.zip, runtime, VC_redist.x64.exe — no engine there. -
Running projects works perfectly, so the engine resolves and executes fine
at runtime — the failure is isolated to the export/packaging code path.
Additional detail (from inspecting the app binary): the embedded manifest
lists the sidecar names together with the actual resource paths:
icons/32x32.png, icons/128x128.png, icons/128x128@2x.png,
icons/icon.icns, icons/icon.ico,
rtila-database, rtila-engine, rtila-relay, rtila-cloudflared
i.e., rtila-engine is referenced by its plain name (no target-triple suffix)
alongside real Resources entries. This is consistent with a build-config
mismatch: the sidecar appears to be declared under resources (so the export
code looks for it in Contents/Resources), while the packaged app actually
places it in Contents/MacOS next to the executable — which is why runtime
works but export doesn’t.
Could you check the engine path resolution in the standalone export? The
same check may be worth doing on the Windows build too.
Thanks!
Alexandre-Kamel
Version 8.3.214 is live now and it includes a fix for the issue reported on Mac. Could you give it a try and let us know if everything looks good on your end? Thanks again for your help and your support!
