This is a known issue and will be addressed in the next update. Apologies for this in the first place.
