I believe this should be fixed in the next update (no ETA, but 'soon').