missingFieldNames

Other cases

• case malformedText

  Text data could not be parsed

• case malformedNumber

  A number could not be parsed

• case trailingGarbage

  Extraneous data remained after decoding should have been complete

• case truncated

  The data stopped before we expected

• case invalidUTF8

  A string was not valid UTF8

• case schemaMismatch

  The data being parsed does not match the type specified in the proto file

• case unknownField

  A field identifier (name or number) was not found on the message

• case unrecognizedEnumValue

  The enum value was not recognized

• case conflictingOneOf

  Text format rejects conflicting values for the same oneof field

• case internalExtensionError

  An internal error happened while decoding. If this is ever encountered, please file an issue with SwiftProtobuf with as much details as possible for what happened (proto definitions, bytes being decoded (if possible)).

• case messageDepthLimit

  Reached the nesting limit for messages within messages while decoding.