The fix was not integrated into the branch used to create the last update; it will be in the next update (no ETA yet).