sachins-geekyants

@kalluriramkumar With the shared at_client branch, the issue is not reproducibile.

@murali-shris I tried sending file between 3 atsigns and none of them were able to download file. I saw similar error msg in terminal , which is shown in screenshot...

when trying to send file from @houseofwaxrural to @adorabledinosaur I was not able receive any notification not even "file_shared_key" notification.

@murali-shris this was on production environment.

on app side I could not capture any logs as I was not getting any notification on receiving end.

@kalluriramkumar I could not reproduce this issue, for me 'privateaccount' key was getting updated only once. Also, sync was not running forever.

@kalluriramkumar we are still facing this issue, do we have any update on this ?

I am running @ mospherePro with at_client:3.0.13 I can still reproduce this issue. The following key was sent by significantredpanda to dying36dragonfly on 9th march 2022. On receiver's end data...

Can still see this issue for ID: `cached:@dying36dragonfly:file_transfer_2b3b7446-7003-40f0-a78c-8f2ad1e00514.mospherepro@significantredpanda ` had a discussion with Sitaram, he pointed >data: [{"id":"7","name":"secondaryServerVersion","value":"3.0.10"}] For some reason the secondary server is running on 3.0.10 version we...

We can not recover the old value but if the server is upgraded to 3.0.12 version, we should not be seeing this issue?