[Bug]: "Encrypted send failed" when sending direct message

[Nikotine1]

Contact Details

No response

Checklist

• I am able to reproduce the bug with the latest version.

• I made sure that there are no existing OPEN or CLOSED issues which I could contribute my information to.

• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.

• This issue contains only one bug.

• I have read and understood the Contribution Guidelines.

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

Affected app version

2.7.1 (29314197)

Affected Android version

Android 15

Affected phone model

Samsung S23 ultra

Affected node model

Home-made Rpi shield with SX1262 modules

Affected node firmware version

Portduino 2.6.11.60ec05e

Steps to reproduce the bug

1. Select this one contact in my contact list
2. Send a direct message
3. Icon shows crossed-out cloud

Actual behavior

Click cloud, message reads: Encrypted Send Failed

This is the only contact this happens with, what is the reason?

Expected behavior

The message is sent and ideally delivered.

Screenshots/Screen recordings

Relevant log output

from: [redacted] (![redacted])
to: [redacted] (![redacted])
id: 3180081625
rx_time: 1759058491
priority: ACK
decoded {
  portnum: ROUTING_APP
  payload: "\030\""
  request_id: 94761420
}

Decoded Payload:
{
error_reason: PKI_FAILED

}

to: [redacted] (![redacted])
id: 94761420
want_ack: true
pki_encrypted: true
decoded {
  portnum: TEXT_MESSAGE_APP
  payload: "Hey"
}

Decoded Payload:
{
Hey
}

Additional information

No response

[DaneEvans]

Is this the 'old firmware unmessageable' bug we had kicking around? meshtastic/Meshtastic-Android#2488

Do you know what firmware that node is on?

Have you tried the other way of messaging in that issue ?

If it's still happening I'll try and get a look at it. but I don't have any firmware that old

[garthvh]

This is a routing error from the firmware, if the app is displaying the message it is handing it properly. There may be an edge case the firmware is not managing properly, transferring there for testing

[garthvh]

@jp-bennett, @thebentern & @GUVWAF this error should happen if the key in the device node db does not match the key stored in the app and being sent on a dm, it seems like it is also being returned (it comes back before the message is actually sent) when the node has rolled out of the device node db. At least that is what I have seen in some limited testing, can we verify / ensure that this is not being returned if there is no matching node in the node db and send out the message?

[Nikotine1]

Do you know what firmware that node is on?

Have you tried the other way of messaging in that issue ?

Unfortunately not, it's not mine.
All I can see it's a Heltec v3, but the firmware section stays empty.

[GUVWAF]

At least that is what I have seen in some limited testing, can we verify / ensure that this is not being returned if there is no matching node in the node db and send out the message?

Indeed it will return this when it is rolled out of the NodeDB. It would be a bit misleading if you still have a green lock, then send a (potentially sensitive) message, which will use the channel key, and only afterwards it turns into an open lock, no?
Instead of the error we could potentially let it ask the client to import the contact?
Ref.:

firmware/src/mesh/Router.cpp

Lines 624 to 625 in 777e11b

	// Client specifically requested PKI encryption
	return meshtastic_Routing_Error_PKI_FAILED;

[Pedrom-pt]

I've the same issue, tested with two differents nodes.

The nodes i want to send an direct message are on my node db.
NO public key mismatch, direct message (RF direct, 0 hop), the message is not delivery "Encrypted send failed"
My Android version: 2.7.1 (google)
My node's firmware 2.6.4

Remote node (1): Firmware 2.6.4
Remote node (2): idk

What i tried: "exchange user info and "Request Metadata"

[jp-bennett]

I think we can actually handle this case by re-adding the contact to the nodeDB from the information provided from the client, and then immediately use that to send the DM.

[Stephan-2025]

I´ve that issue too since update on Android to 2.7.1 APP Version on a RAK Device (Firmware 2.6.6), which worked fine bevor the update of the App.
Also deleting the contact out of my node db don´t solve it.

The encryption-sign is green ... but i´m able to send messages out in channel - no problem there.
I also tried another random mesh node in my list (to send a PN) - the same PN Send-Problem.
But only PNs are no more possible to send, on channels everything works fine

[github-actions]

This issue has not had any comment or update in the last month. If it is still relevant, please post update comments. If no comments are made, this issue will be closed automagically in 7 days.

[tbeam915]

Bump, still having this issue 2.17.xx, @&#! off @github-actions

Android Client