Summary

• raise PacketSize.selfInfoMinimum from 55 to 57 bytes
• add coverage for the minimum valid fixed-width SelfInfo payload and for truncated payload rejection

Why this is the correct fix

The current MeshCore firmware documentation describes PACKET_SELF_INFO as:

• byte 0: packet type
• bytes 1-57: fixed-width fields through radio spreading factor and coding rate
• bytes 58+: optional device name

References:

• https://github.com/meshcore-dev/MeshCore
• https://github.com/meshcore-dev/MeshCore/tree/main/docs
• docs/companion_protocol.md (PACKET_SELF_INFO)

PacketParser drops the response code before parsing, so the parser should require a minimum payload length of 57 bytes, not 55. With the old boundary, malformed frames missing radioSF/radioCR could still pass the initial size check and then be parsed incorrectly.

This change tightens validation to match the documented fixed-width frame while preserving valid firmware behavior, including payloads with no trailing device name.

Testing

Automated:

• cd MeshCore && swift test
• Result: 262 tests passed in 23 suites
• Added tests cover:
  • valid 57-byte SelfInfo payload with no device name
  • invalid truncated 55-byte SelfInfo payload rejected with parse failure

Manual on device:

• launched the app on an iPhone 16 Pro over USB from Xcode
• paired and connected successfully to a MeshCore device
• confirmed normal session startup, selfInfo reception, sync, and repeater interaction all still work

Relevant log proof from the successful on-device run:

Received event: selfInfo(MeshCore.SelfInfo(... name: "RKE2847"))
MeshCore session started
Received event: deviceInfo(MeshCore.DeviceCapabilities(firmwareVersion: 10, ... version: "v1.14.0-9f1a3ea" ...))
Full sync complete
Connection complete - device ready
[CMD] <- REPEATER CLI_RESP from=88fcce4bf302 resp="v1.14.0-9f1a3ea (Build: 06-Mar-2026)"

That gives both sides of the validation: the new parser still accepts real firmware frames on hardware, and the new tests prove truncated frames are rejected.