Thanks for testing out the new version again, and sharing your feedback! My apologies that it didn’t solve your issue.
As it turns out, I made a mistake and did not fully include the fix for your issue in the latest release, so thanks for catching that!
I’ve released a new update with the fix (v2.12.3), which you can download here.