Probably caused by a packaging bug that created the 'data' directory in the Contents/MacOS directory as an ASCII file instead of a symlink. App will fail to launch with this defect.
Stable workaround was to move aside 'data' file and create a same named symlink to ../Resources/data.
Probably caused by a packaging bug that created the 'data' directory in the Contents/MacOS directory as an ASCII file instead of a symlink. App will fail to launch with this defect.
Stable workaround was to move aside 'data' file and create a same named symlink to ../Resources/data.