It seems this is resolved on current application version once it re-opens.