This will be fixed in a future update (no ETA). I don't know of any workarounds.