SyncAdapter: Hilt error handling #1299
Merged
+80
−23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After a lot of playing around and testing, I chose the simplest modification to work around the problem. I think it can't be completely avoided that syncs are called (except when we would use a "test account" account type for testing, but then we would test something else that we'd use in the real app).
Short description
SyncAdapterServices
, so that the tests don't fail when such an (unwanted) sync is started.sync_calendars.xml
to explain whatisAlwaysSyncable
really does.SyncAdapter
constructor to explain whatautoInitialize
really does.CC @sunkup