Unfortunately, there isn't a workaround possible, so the fix will need to wait until the next update. There is no ETA yet.