Hi,
I’m a Mac administrator at Loughborough University, deploying Twinmotion 2026.1.0 across our Mac lab fleet via Jamf Pro. I wanted to report an installer issue we’ve had to work around.
The Mac installer for 2026.1.0 includes an ExportCloud.pkg component, which is expected to run a postinstall action creating a configuration file at:
$TM_APP/Contents/UE/Twinmotion/Binaries/Mac/StaticConfig/online.cloudpublishing
containing the installed version number (e.g. “2026.1.0”). In our testing, this postinstall step does not run during a standard installation - the StaticConfig directory and online.cloudpublishing file are simply absent after installation completes, regardless of installation method (manual, or via Jamf policy).
Without this file present, the installation ultimately fails to complete fully.
To work around this on our end, we’ve written our own postinstall script that replicates what ExportCloud.pkg’s postinstall action should be doing:
#!/bin/bash
TM_APP=“/Applications/Twinmotion.app”
TM_VERSION=“2026.1.0”
TM_CONFIG_DIR=“$TM_APP/Contents/UE/Twinmotion/Binaries/Mac/StaticConfig”
TM_CLOUD_FILE=“$TM_CONFIG_DIR/online.cloudpublishing”
if [[ -d “$TM_APP” ]]; then
mkdir -p “$TM_CONFIG_DIR”
echo “$TM_VERSION” > “$TM_CLOUD_FILE”
echo “Created $TM_CLOUD_FILE”
else
echo “Twinmotion.app not found. Exiting.”
exit 1
fi
exit 0
This runs as a postinstall step in our own deployment policy and resolves the issue for us, but it shouldn’t be necessary - this is functionality the official installer is supposed to handle itself via ExportCloud.pkg.
Could you confirm whether this is a known issue with the 2026.1.0 Mac installer, and whether a fix is planned for an upcoming release? Happy to provide further detail on our environment (macOS version, deployment method, Jamf Pro) if that would help with reproducing this on your end.
Thanks,
David Taylor
Mac Administrator, IT Services
Loughborough University