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.

[sentry]

Sentry Issue: UNITY-EXPLORER-PH1

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.
  File "DCL.RPC.cpp", line 269, in pb::Google.Protobuf.IBufferMessage.InternalMergeFrom
  File "DCL.RPC.cpp", line 11731, in pb::Google.Protobuf.IBufferMessage.InternalMergeFrom
  File "Generics__28.cpp", line 34583, in Remove
  File "Generics__28.cpp", line 20462, in Remove
  File "il2cpp-codegen.h", line 69, in ParseProtocolMessage
...
(26 additional frame(s) were not displayed)

This issue was automatically created by Sentry via Explorer Alpha Github Issue Creation

[github-actions]

Automated Triage

Issue type	bug
Affected area	RPC Protocol Buffer Deserialization
Feature category	Primary (Stability & Crashes)
Severity	SEV-2 → 1-high

Reasoning: This is a crash occurring during RPC protocol buffer parsing, which falls under the Primary category of Stability & Crashes. The exception suggests either truncated data or a message length mismatch in the serialization layer. While crashes are primary-category issues, the description does not indicate this affects "most users" or blocks the entire platform, so this is classified as SEV-2 affecting some users rather than SEV-1. The issue warrants investigation into potential malformed protocol buffer data in the asset bundle request/response flow.

Labels applied: bug, 1-high, sentry

---

Auto-triaged. If labels are incorrect, update issue triage categories or severity policy and re-run triage.

[github-actions]

This is a duplicate of #7721 (and #8543). All three issues report the same Google.Protobuf.InvalidProtocolBufferException when parsing protocol messages with truncated or malformed fields.

Please follow issue #7721 for updates on this problem and any fixes that may be implemented.

Thanks for reporting!

[github-actions]

Automated Triage

Issue type	bug (crash)
Affected area	RPC protocol / Network communication
Feature category	Primary (Stability & Crashes)
Severity	SEV-2 → 1-high

Reasoning: This is a protobuf parsing exception occurring in production (caught by Sentry) in the RPC communication layer. Protocol buffer parsing failures in core communication are classified under the Primary category "Stability & Crashes," making this a SEV-2 issue. The exception indicates either truncated input or a message length mismatch, which could affect multiple users' ability to communicate with the backend. The issue is already marked as a duplicate, indicating it's a known problem being tracked elsewhere.

Labels applied: bug, 1-high, sentry, duplicate

---

Auto-triaged. If labels are incorrect, update issue triage categories or severity policy and re-run triage.