@kerryeva This issue is related to bug on our end and we are aware of that. Fix should be out in our next version of app.