Use of try! should be avoided

[tapwork]

During my Unit Tests I had some crashes that are caused by an error during CoreData save

public func save() {
        try! persistentStore.save()
    }

I saw plenty of places in the SynchronizationManager where error handling is ignored / disabled by the usage of try!.
Why don't you properly use do-catch or just try?.
But try! should only be used if you're certain that there is no error thrown

See: #26

[loudmouth]

Fixed in #26