Purnima

Behavior of SDK on different network scenarios has been documented in the [sheet](https://github.com/atsign-foundation/at_client_sdk/issues/594)

I was able to replicate this issue only when the network is down. Steps I followed - Switched off the network - I could see the error in the app...

The null safety issue on dart:Indexed_db is from a package that is blocked by flutter. See the following link for reference. https://github.com/dart-lang/pana/issues/891 Hence moving this issue to backlog

Refactored the tests and pushed the changes to the [refactor_tests](https://github.com/atsign-foundation/at_client_sdk/tree/refactor_tests)

Refactored some more tests and pushed the changes to the same branch. [refactor_tests](https://github.com/atsign-foundation/at_client_sdk/tree/refactor_tests)

Refactoring tests are done, The tests are failing in the GitHub actions that need to be looked at. Draft PR - (#774 )

The performance tests include - [x] Notification text latency **What are we measuring**: These tests measure the latency/time difference between the time that the notification is sent from the sender's...

The design isolates part is pending in the ticket. That can be tracked as part of the ticket [Build ticket](https://github.com/atsign-foundation/at_client_sdk/issues/734)

Verified the changes with atMospherePro app and latency tests. 1. With atMosphere pro app, - With an old atsign the _latestNotificationIdv2 was available for the first time, But later the...

Raised a [PR](https://github.com/atsign-foundation/docs.atsign.com/pull/154) for the following changes. - AtClientManager - discuss notification service and sync service before stating how to fetch it using AtClientManager - Key Basics - Remove "in...