I can confirm this will be fixed in the upcoming 4.3.9 update 🙂