Protocol message tag had invalid wire type

io.grpc.StatusRuntimeException: INTERNAL: Invalid protobuf byte sequence
	at io.grpc.Status.asRuntimeException(Status.java:534)
	at io.grpc.protobuf.lite.ProtoLiteUtils$2.parse(ProtoLiteUtils.java:173)
	at io.grpc.protobuf.lite.ProtoLiteUtils$2.parse(ProtoLiteUtils.java:94)
	at io.grpc.MethodDescriptor.parseRequest(MethodDescriptor.java:293)
	at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.messageRead(ServerCallImpl.java:243)
	at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1.runInContext(ServerImpl.java:555)
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:52)
	at io.grpc.internal.SerializingExecutor.runSerializingExecutor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.google.protobuf.InvalidProtocolBufferException$InvalidWireTypeException: Protocol message tag had invalid wire type.
	at com.google.protobuf.InvalidProtocolBufferException.invalidWireType(InvalidProtocolBufferException.java:115)
	at com.google.protobuf.CodedInputStream$ArrayDecoder.skipField(CodedInputStream.java:692)
	at com.yxbj.service.grpc.payment.ITunesNotificationRequest.<init>(ITunesNotificationRequest.java:53)
	at com.yxbj.service.grpc.payment.ITunesNotificationRequest.<init>(ITunesNotificationRequest.java:9)
	at com.yxbj.service.grpc.payment.ITunesNotificationRequest$1.parsePartialFrom(ITunesNotificationRequest.java:2000)
	at com.yxbj.service.grpc.payment.ITunesNotificationRequest$1.parsePartialFrom(ITunesNotificationRequest.java:1995)
	at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:91)
	at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:49)
	at io.grpc.protobuf.lite.ProtoLiteUtils$2.parseFrom(ProtoLiteUtils.java:178)
	at io.grpc.protobuf.lite.ProtoLiteUtils$2.parse(ProtoLiteUtils.java:170)
	... 9 more
"},
"threadContext":{}}

com.google.protobuf.InvalidProtocolBufferException: Protocol message end-group tag did not match expected tag.

com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero).

com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either that the input has been truncated or that an embedded message misreported its own length.

[ejona86]

@vaikzs, “Protocol message had invalid UTF-8.” Either the remote sent you an invalid proto or there was corruption on-the-wire. To help at all we’d need to know more of how this was triggered. It’s useful to know whether this is reproducable, used TLS, and what client/server/proxy implementations were involved.

[ejona86]

Can you provide more information about how this occurred? These exceptions normally mean either 1) corruption or 2) you aren’t parsing a protobuf. Is this seen on client or server, and what is the remote software being used? What is done to trigger this?