I believe this issue was fixed in a Patreon version. It should be pushed to the public update when the fix rotates out of the exclusive updates. (I'll take another look none the less though in case it's an all-new error)