We have confirmed that the issue has been addressed in both beta 6 and beta 7. Thank you.