Because of changes in Fabric 2.3.3 GRPC message size must be configurable via peer.maxSendMsgSize changelog
But in chaincode client it is hardcoded to 100M: https://github.com/hyperledger/fabric-chaincode-go/blob/main/shim/internal/client.go#L19
Peer must provide actual size to chaincode while building container (via env for example like it is done with CORE_PEER_TLS_ENABLED) and chaincode server must read it.
Because of changes in Fabric 2.3.3 GRPC message size must be configurable via peer.maxSendMsgSize changelog
But in chaincode client it is hardcoded to 100M: https://github.com/hyperledger/fabric-chaincode-go/blob/main/shim/internal/client.go#L19
Peer must provide actual size to chaincode while building container (via env for example like it is done with CORE_PEER_TLS_ENABLED) and chaincode server must read it.