This was fixed in a previous update. Marking as resolved. If user is still seeing this bug - they can reopen.