This issue will be fixed in the next update (no ETA yet, but it is currently being prepared/tested).