Sitaram Pavan Kumar Kalluri

Fixed the issue and the changes are available in https://github.com/atsign-foundation/at_client_sdk/pull/666. Request the apps team/QA team to test the changes. The changes are available in `fix_auth_issue` in at_client_sdk repo.

> @kalluriramkumar With the shared at_client branch, the issue is not reproducibile. @sachins-geekyants : Great, Can you please confirm the regression tests are also covered?

The changes are published in at_client_mobile : 3.2.5

Added end2end tests for in for put and get methods in at_client

Investigated the issue and below are the observations: 1. When an atsign is reset, the PKAM public key in server is lost. When the network is down, the client fails...

Debugged this issue on .wavi - This is because the put request is being invoked by the wavi app continuously. The key 'privateaccount' is getting updated in a loop as...

> **Is your feature request related to a problem? Please describe.** > > * if sync regex of an app changes after it was created, behaviour of sync has to...

Updated the sync regex in between and tested using code samples and below are the observations: After the sync regex is updated, the keys that match the updated regex criteria...

@sarika01: I have debugged the issue using blindtahugejrot staging atsign (atsign which @sachins-geekyants provided), The secondary server of the atsign keeps restarting and hence the SocketException

Had call with @sachins-geekyants and below are the initial analysis from the secondary server logs. Looks like when running TTR job if empty data is received, the keys are updated...