Thank you!
Yea.. we already encountered this bug and fixed it. Too bad we couldn't upload the fix in time.
