Muralidharan

@cconstab Is the below code snippet similar to what you were trying ? ``` var currentAtSign = '@alice🛠'; var sharedWithAtSign = '@bob🛠'; final metaData = Metadata()..ttl = 10000; var phoneKey...

@cconstab Issue # 2 is fixed in at client v3.0.30 Regarding # 3, are you seeing the notification twice on receiver's secondary server or receiver's client side ?

@cconstab can you please re-check this scenario with latest at_client version

@sachins-geekyants are you still facing this issue ?

@nitesh2599 did you also face "invalid or corrupted pad block" exception as reported by Purnima?

@sachins-geekyants is this bug still valid?

@ralfeus Thanks for sharing the logs. I am trying to replicate your issue in my local environment. I will keep you updated with my findings.

Updates from my local testing: 1) there is discrepancy in the way keys are added in metadata cache in create and put methods of hive_keystore.in put method we are not...

@ralfeus do you have local secondary server setup where you can run your client pointing to local server?

pending addressing some review comments and PR merge.