tree c5b15387405450cb239353b3e90e41aeb5b05a06
parent 55eb65eeb2191b81353d771a766addf3b664c363
author Samiul Islam <samiul@google.com> 1661427138 +0100
committer Samiul Islam <samiul@google.com> 1661443191 +0100

Remove concept of "stop" state from SharedPreferencesSyncManager

We have removed stop() api and removed callbacks for notification of
error. The idea is that SyncManager will deal with all errors internally
without putting any burden to the user.

There can be two kind of errors: sandbox is unavailable and everything
else.

If sandbox is unavailable, we should move to a waiting state and resume
syncing once it is available.

For all kinds of other errors, log the error and just keep on syncing.
Ideally, there should be no errors at all. If there are any, we have to
fix them to gurantee seamless syncing.

If user wants to stop syncing, they can just remove all the keys from
sync pool. API for removal of keys will be added soon.

So there is only two state for SyncManager now: running and waiting.
That can be figured by a single boolean, so refactored accordingly.

Bug: 239403323
Test: atest SdkSdkSandboxFrameworkUnitTests
Change-Id: Ibe0b75b95c38125711bc5726dee30b6693ad06c4