This fix was folded into build 002 on March 18. If you downloaded build 002 on March 16 or 17, it did not include this fix.
In general, we allow a 48-hour period after initial publishing of a build where new reports can be folded into the same build -- you may recall reports where I've said "Fixed in the current build" or something like that. After 48-hours, the fix must wait until a new release or a new build.