Looks like this issue is actually fixed in your beta version

I'm glad the new version has resolved it.