Found a workaround that can avoid the framework bug mentioned above.
Released v5.6.5:
Thanks again for reporting!