Just to let you know there is a fix proposed by the developer, which will need to undergo the normal code review and testing steps before it is available, but it is in hand.
According to the internal ticket it just passed testing, so the developer just has to complete the process of merging into the release branch so that it is included in the next update, and that is due together with other plugins by the end of this month.
I was just reviewing escalated tickets for today's plugin updates and see I didn't update this earlier when the fix was released in the last set of updates.
If you haven't already, updating will fix this issue.