nl: when the login machine terminates , we might not be in the married state , and therefore we ca n't sync . this method messages as much to the user . to avoid stopping us syncing altogether , we set a soft error rather than a hard error . in future , we would like to set a hard error if we are in , for example , the separated state , and then have some user initiated activity mark the android account as ready to sync again . this is tricky , though , so we play it safe for now . concode_field_sep BlockingQueue<Result> latch concode_elem_sep SyncResult syncResult concode_field_sep void setSyncResultSuccess concode_elem_sep void postponeSync concode_elem_sep void setSyncResultSoftError concode_elem_sep void handleError concode_elem_sep void handleSuccess concode_elem_sep void rejectSync concode_elem_sep void setSyncResultHardError
code: void function ( State arg0 ) { setSyncResultSoftError ( ) ; latch . offer ( Result . Error ) ; }