Yes,The released SDK4.2 snapshot has this issue, we have fixed it, please use the new firmware to verify.