Can confirm building a newer version of Bino (I used the latest 1.6.1) removes this bug. Can we not got just re-compile a later version of Bino and package it to resolve and close this bug?
Can confirm building a newer version of Bino (I used the latest 1.6.1) removes this bug. Can we not got just re-compile a later version of Bino and package it to resolve and close this bug?