Thanks for the feedback! Some players in the community reported this shortly after the update too. The bug was fixed about 10 minutes after the 1.4.0 update went live.
