Thank you for reporting this issue. We’ve identified the cause regarding binary execution paths and have urgently released version 0.1.6 to address it.
Please update to the latest version and try running your executable again. We appreciate your patience!