🐞 [Bug]: Cannot see direct messages

[goyaweb]

Before submitting

• [x] I have searched existing issues to make sure this bug hasn't already been reported
• [x] I have updated to the latest version of the software to verify the issue still exists

Firmware Version

2.6.2

What did you do?

First time user. Send a direct message to a node next to me. Receive a message back.

Expected Behavior

message sent can be seen, message received can be seen.

Current Behavior

As soon as I hit send my message disapears but arrives as recipient. When I receive an answer I get a notification but when opening the direct message the screen is empty again.

Strange other thing is that when I go out of range of my own node or turn it off I get an extra Contact in my direct message list with the name of my node. When opening this contact I can then see the whole conversation but can't see with whom it was. The contact i was having the conversation with remains having only an empty screen.

Participation

• [ ] I am willing to submit a pull request for this issue.

Additional comments

No response

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[Whatnoww]

Having this particular issue.

Adding some context that this seems to happen when a node is first seen locally and then over mqtt. I have two sensecap t1000e where ocasionally I will have the node on iOS show up with user data, then a while later it'll also show up as a node without a key exchange. Can't reproduce this behavior on Android with the same node.

[Whatnoww]

Yep, as suspected, this code here seems to apply universally and seems to be the root cause: https://github.com/meshtastic/Meshtastic-Apple/pull/814/commits/045bd7124af1a58bfa68efadf7fd16abce2951d7

Not sure why this was applied universally to all mqtt servers. My private one should not have the iOS app enforcing a 0 hop limit by removing a contact from the chatlist.

[razorseal]

Having the same issue. However I am getting notifications showing that message came. Also the chat bubble at bottom right shows the notification and there's no way to erase it out. Only solution is to reinstall. Running latest apk and ios and firmware on the two t1000e

[RCGV1]

@goyaweb @razorseal @Whatnoww What iOS app version were you on when this occurred?

[razorseal]

iOS 18.5 for me

On Fri, May 23, 2025 at 21:31 Benjamin Faershtein @.***> wrote:

RCGV1 left a comment (meshtastic/Meshtastic-Apple#1229) https://github.com/meshtastic/Meshtastic-Apple/issues/1229#issuecomment-2906261042

@goyaweb https://github.com/goyaweb @razorseal https://github.com/razorseal @Whatnoww https://github.com/Whatnoww What iOS app version were you on when this occurred?

— Reply to this email directly, view it on GitHub https://github.com/meshtastic/Meshtastic-Apple/issues/1229#issuecomment-2906261042, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIGVD4XZWQOQDAPFPICBXFL277DVTAVCNFSM6AAAAAB5KXE7H6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBWGI3DCMBUGI . You are receiving this because you were mentioned.Message ID: @.***>

[RCGV1]

@razorseal The Meshtastic app version not iOS version

[razorseal]

Oops sorry about that. I’m on 2.6.2 (1421)

On Fri, May 23, 2025 at 22:54 Benjamin Faershtein @.***> wrote:

RCGV1 left a comment (meshtastic/Meshtastic-Apple#1229) https://github.com/meshtastic/Meshtastic-Apple/issues/1229#issuecomment-2906328922

@razorseal https://github.com/razorseal The Meshtastic app version not iOS version

— Reply to this email directly, view it on GitHub https://github.com/meshtastic/Meshtastic-Apple/issues/1229#issuecomment-2906328922, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIGVD4RQ5H4C4DJYLS6FE5D277NPZAVCNFSM6AAAAAB5KXE7H6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBWGMZDQOJSGI . You are receiving this because you were mentioned.Message ID: @.***>

[RCGV1]

Can you guys capture logs when this happens by going to settings (bottom) logs

[RCGV1]

Also please enable firmware debug logs

[luu176]

When I receive a message and it isn't displayed on my DMs (like a ghost message)

[luu176]

Is this bug being fixed? I can't see any messages with some people

[RCGV1]

@luu176 Thanks for the logs, can you also display debug logs

[luu176]

I sent them two days ago in this issue

[luu176]

aren't the logs I sent debug logs? it says debug logs

[Dimonstar]

I see the same issue between my nodes. On one node messages are not visible in DM messages view however notification for the message is being shown. Attaching logs and screenshots. Firmware: 2.6.4 on both nodes. iOS app version 2.6.3

This might have something to do with changing node's name (long and short) as I couldn't reproduce after reseting devices and leaving default names.

Meshtastic Application Logs.csv

[RCGV1]

I don't see anything in the logs which is out of the ordinary (I think), to solve this issue we need to be able to reliably recreate it. If anyone is able to do a little exterminating, getting steps to recreate it would be very appreciated.

[luu176]

It is very reproducible, it happens on all of my friend's phones if they are IOS, if you have an iphone just try DMing someone and it might not work, it's like a 1/10 chance. it happens mostly when the lock emoji is open next to the name of the node (meaning unknown public key) you are texting. If you want me to do more tests just let me know the steps and i'll send whatever you need.

[Dimonstar]

Same experience here. Reproduces each time.

1. Using 2 new nodes, one connected to iOS another to macOS over bluetooth.
2. Setup up both nodes with defaults settings (USA, Long-Fast).
3. Message primary channel from one of the nodes to speed up discovery.
4. Text from one node to another with DM and attempt to reply from another node.

Result: For one of the nodes in iOS/macOS app, messages view will be empty even though messages are being delivered to another node.

[RCGV1]

@Dimonstar do both of these nodes have each other's keys?

[Dimonstar]

@RCGV1 how can I verify this? Do I have to do anything special for them to exchange keys like scan QR code?

[RCGV1]

@Dimonstar do the nodes have a locked or unlocked icon next to them in the node list or messaging list?

[RCGV1]

Never mind I see it in the screenshot

[luu176]

so is there a fix?

[RCGV1]

Tell me if this issue occurs theres been an update to the dms sreen

[mangelajo]

I have also been hitting this sometimes, only an app db reset will fix it

[jeromegv]

hitting the same issues.. only started once i renamed my device name (long and short) as @Dimonstar mentioned

@mangelajo how do you do a app db reset?

[va3jme]

I have had this issue, under a very specific condition.

• Add a new node to my favorites list
• Send and receive between me and new node, no problem
• Re-flash new-node, but do NOT update key in new node to be the same as it was before, in other words, it has a different key
• Send messages from me to new node, they will be accepted
• New node sees that a message came in, but it is not showing in the DM

The fix is to delete the new node from your system... possibly even reset your node-db. Then on the "new node" you download the key that was used when you created the node the first time. Now things should work fine. This is why you should always back up your key.... if you ever need to re-flash, and you want everyone to still be able to reach you, you will need to use the same key you always used.

Hope that is clear

Tested with three different phone (2 iOS, 1 android) and three Seeedstudio SenseCap T1000E units. Multiple tests confirm for me anyway that this fix works.

[garthvh]

As of 2.6.12 he notifications for emoji have been updated so that they link to the message they are attached to, unmessagable nodes that have sent or received messages are now visible and there is no MQTT hops based filtering anymore.

[holgerscherer]

bug is still in macos app ver 2.6.15 can't tell about who is the sender because i did not get notifications.

[holgerscherer]