Bug? Messages show as “Meshtastic xxxx”before nodes finish syncing + Unreadable

[mjtullio]

Hi everyone, I’m running into a strange issue with my Heltec V3 (firmware 2.6.11) connected via WiFi TCP in the new iOS app.

When I connect, I instantly receive incoming messages (MQTT or LoRa), but the node is still syncing in the retrieving nodes process. If a message arrives before syncing is complete, it shows up as coming from “Meshtastic xxxx” instead of the configured custom name and short name. After the sync finishes, the contact list displays the node correctly with its custom name and short name. However, those earlier messages remain unreadable:

They don’t appear in the messages section (though the unread counter increases).
I cannot read or reply to them.
I tested this with another node of mine, a Heltec T114. Messages sent from the V3 to the T114 work fine. But if the T114 sends to the V3, the V3 device screen shows the correct short name, while in the iOS app the message still appears as from “Meshtastic xxxx”, and the same issue happens.

My guess is that the iOS app hasn’t finished syncing the node info internally, so at the time the message arrives, it only knows the node as “Meshtastic xxxx”, even though the V3 device screen display the message and short name correctly.

On the other hand, I connect via Bluetooth with the same phone and app to the T114 node and the names and messages work just fine.

Vía Bluetooth on my T114 I’ve noticed that the app syncs the nodes first, then the messages so I still have no clue why the TCP connection in my V3 sync the other way around.

Has anyone else seen this behavior on iOS? Could it be a known bug, or am I missing a config step?