jbwpdw19

Hi! Yes, if you roll back to version 2.1.1 the issue is fixed 🙂 and I hope that the development team is working on solving this problem, once and for all.