hyperledger/fabric · error

no proposal responses received

Error message

no proposal responses received

What it means

Defensive check in Approve: after iterating all endorser clients, the responses slice is empty. The code comment notes this "should only be empty due to a programming bug" — EndorserClients was initialized with zero entries — so this is an internal invariant failure, not an expected runtime condition.

Source

Thrown at internal/peer/lifecycle/chaincode/approveformyorg.go:186

	}

	signedProposal, err := signProposal(proposal, a.Signer)
	if err != nil {
		return errors.WithMessage(err, "failed to create signed proposal")
	}

	var responses []*pb.ProposalResponse
	for _, endorser := range a.EndorserClients {
		proposalResponse, err := endorser.ProcessProposal(context.Background(), signedProposal)
		if err != nil {
			return errors.WithMessage(err, "failed to endorse proposal")
		}
		responses = append(responses, proposalResponse)
	}

	if len(responses) == 0 {
		// this should only be empty due to a programming bug
		return errors.New("no proposal responses received")
	}

	// all responses will be checked when the signed transaction is created.
	// for now, just set this so we check the first response's status
	proposalResponse := responses[0]

	if proposalResponse == nil {
		return errors.New("received nil proposal response")
	}

	if proposalResponse.Response == nil {
		return errors.Errorf("received proposal response with nil response")
	}

	if proposalResponse.Response.Status != int32(cb.Status_SUCCESS) {
		return errors.Errorf("proposal failed with status: %d - %s", proposalResponse.Response.Status, proposalResponse.Response.Message)
	}
	// assemble a signed transaction (it's an Envelope message)

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Ensure Init (setPeerClients) succeeded and populated EndorserClients with at least one peer before Approve runs
2. Check that -peerAddresses was supplied and passed validation
3. If it persists, treat as a bug in command initialization and report with the full command invocation

When it happens

Trigger: Thrown at internal/peer/lifecycle/chaincode/approveformyorg.go:186 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of hyperledger/fabric@2736b63f8f (2026-09-04). Data as JSON: /api/errors/546c177f1ae7c829. Report an issue: GitHub.