@Mauliks If you could update to the latest version of Reader SDK 1.5.2 that should resolve the issue.