I have identified another (related) cause for this and made a new version 2.1.0.107 that should fix it.