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

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by gary-rowe
, 1 year ago
While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either than the input has been truncated or that an embedded message misreported its own length.
via GitHub by sambanks
, 2 years ago
While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either than the input has been truncated or that an embedded message misreported its own length.
via GitHub by xzy256
, 5 months ago
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.
via Stack Overflow by mayank
, 2 years ago
While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either than the input has been truncated or that an embedded message misreported its own length.
via programmershare.com by Unknown author, 1 year ago
While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either than the input has been truncated or that an embedded message misreported its own length.
via Stack Overflow by shylas
, 1 year ago
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
com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either than the input has been truncated or that an embedded message misreported its own length.
at com.google.protobuf.InvalidProtocolBufferException.truncatedMessage(InvalidProtocolBufferException.java:70)
at com.google.protobuf.CodedInputStream.readRawBytes(CodedInputStream.java:854)
at com.google.protobuf.CodedInputStream.readBytes(CodedInputStream.java:329)
at com.google.protobuf.UnknownFieldSet$Builder.mergeFieldFrom(UnknownFieldSet.java:484)
at org.bitcoinj.wallet.Protos$Wallet.(Protos.java:14465)
at org.bitcoinj.wallet.Protos$Wallet.(Protos.java:14423)
at org.bitcoinj.wallet.Protos$Wallet$1.parsePartialFrom(Protos.java:14626)
at org.bitcoinj.wallet.Protos$Wallet$1.parsePartialFrom(Protos.java:14621)
at com.google.protobuf.AbstractParser.parsePartialFrom(AbstractParser.java:200)
at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:217)
at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:223)
at org.bitcoinj.wallet.Protos$Wallet.parseFrom(Protos.java:15469)
at org.bitcoinj.store.WalletProtobufSerializer.parseToProto(WalletProtobufSerializer.java:538)
at org.multibit.hd.core.managers.WalletManager.loadWalletFromFile(WalletManager.java:692)
at org.multibit.hd.core.managers.WalletManager.loadFromWalletDirectory(WalletManager.java:739)
at org.multibit.hd.core.managers.WalletManager.getOrCreateTrezorSoftWalletSummaryFromSeedPhrase(WalletManager.java:476)
at org.multibit.hd.ui.views.wizards.welcome.restore_wallet.RestoreWalletReportPanelView.createWalletFromSeedPhraseAndTimestamp(RestoreWalletReportPanelView.java:444)
at org.multibit.hd.ui.views.wizards.welcome.restore_wallet.RestoreWalletReportPanelView.handleRestoreWallet(RestoreWalletReportPanelView.java:334)
at org.multibit.hd.ui.views.wizards.welcome.restore_wallet.RestoreWalletReportPanelView.access$000(RestoreWalletReportPanelView.java:64)
at org.multibit.hd.ui.views.wizards.welcome.restore_wallet.RestoreWalletReportPanelView$1.run(RestoreWalletReportPanelView.java:166)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
5 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.