[Bug]: Regression: Public Key Mismatch Issue reappeared with Heltec Node V3.2 and V4 on latest Android (2.7.10) and iOS (2.7.6) apps

[Ron252525]

Contact Details

myenglish69@googlemail.com

Checklist

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

• I have updated to the latest Alpha firmware, and am able to reproduce the bug. Many issues are fixed quickly in alpha before the general beta release.

• 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

• I actually read this list, and should be taken seriously.

Affected app version

Android App 2.7.10 Google Store, iOS App 2.7.6 Apple Store

Affected Android version

Android 13, UI Core 5.1

Affected phone model

Samsung Galaxy A22 5G

Affected node model

Heltec V3.2, Heltec V4

Affected node firmware version

2.7.15.567b8ea Beta

Steps to reproduce the bug

The previously reported issue has reappeared.

I can reproduce the same problem again with Heltec Node V3.3 and V4 using the latest mobile apps:

Android app 2.7.10 (Google Play)

iOS app 2.7.6 (Apple App Store)

This is a regression of the earlier bug reported here:
#1742

Nothing in the setup has changed except updating the mobile apps. Behavior is identical to the original issue.

Steps to Reproduce:

1 Flash last firmware on the fresh hardware
→ No connections in db.

2 Rename the node with two new names.
→ No connections in db.

3 Set region to EU 868.
→ No connections in db.

4 Store / save keys.
→ No connections in db.

5 Communicate on LF0.
→ first connections in db.

6 Communicate with other nodes via Direct Messages (DM).
→ Everything works as expected. DM works.

7 Clean the database and perform a factory reset in Apps.
→ No connections in db.

8 Re-flash the node with Full Erase.
→ No connections in db.

9 Change the node name again to old names.
→ No connections in db.

10 Import the previously saved keys.
→ No connections in db.

11 Communicate on LF0.
→ first connections in db.

12 Try to communicate via Direct Messages (DM) to known nodes
→ Error occurs with Red Key, my node resend shared secret key recalculated from my imported public keys.

13 No DM connection to old known node "Cloud with Slesh", prompt "No Channel"

Actual behavior

No DM connection to old known node, prompt "No Channel"
It happens even with new node names and new keys after reflash with full erase

Expected behavior

DM connection to old known node with old names and old imported keys

Screenshots/Screen recordings

No response

Relevant log output

Additional information

Samsung Galaxy A22 5G with Android 13, UI Core 5.1
iPhone SE 2022 with iOS 26.2

[github-actions]

Thank you for your detailed report! It looks like you've covered a lot of important aspects, but it seems that the actual log output section is empty, and you haven't provided any screenshots or screen recordings. These could be helpful for the developers to understand and troubleshoot the issue effectively.

Could you please provide any relevant log outputs that you might have? If you have any screenshots or screen recordings demonstrating the issue, those would also be valuable additions. Thank you again for your effort in reporting this!

[Ron252525]

[Ron252525]

Log:

from: 2896850544 (!acaa6e70)
to: 4294967295 (!ffffffff)
id: 3981502706
rx_time: 1767712646
hop_limit: 5
priority: BACKGROUND
decoded {
portnum: TELEMETRY_APP
payload: "\r\206']i2 \b\355\275\004\035\237\032O> \213\001(\277\t0\0028\026@PH\232\002`\300\306\017h\374\234\004"
}

Decoded Payload:
{
time: 1767712646
local_stats {
uptime_seconds: 73453
air_util_tx: 0.20224999
num_packets_tx: 139
num_packets_rx: 1215
num_packets_rx_bad: 2
num_online_nodes: 22
num_total_nodes: 80
num_rx_dupe: 282
heap_total_bytes: 254784
heap_free_bytes: 69244
}

}

[b8b8]

where's the screenshot from the iphone showing what public key its storing from the android node?

[Ron252525]

@Bibi: I don't have it anymore. This is an Android App issue and an Apple App issue, not a meshtastic firmware or hardware issue.
#1742

[b8b8]

right but is the apple app showing a key mismatched from your android node?

does deleting the android node from the apple node and reacquiring the key solve the issue?

show both setups next to each other with their keys being incorrect.

[Ron252525]

I have two phones, Android and iPhone, and I had tested this with two nodes coupled to both and communicated with others:
in IPhone after DM red sign and prompt "no channel" to see,
in Android after DM cloud with slash and after typing on cloud "no channel".

When I communicate between my two nodes, I have the same problem on the transmitter side.
At the receiver I see an input with "wrong key" (at iPhone) without message, then I have to push "wrong key" (must make action) and it starts working from the next message

[Ron252525]

Deleting nodes didn't help

[Ron252525]

"show both setups next to each other with their keys being incorrect" - Keys are correct but the key-session-number (n+1) must be wrong

[garthvh]

"show both setups next to each other with their keys being incorrect" - Keys are correct but the key-session-number (n+1) must be wrong

There is no session number involved in messaging

[Ron252525]

Then it must be a bug in Apple and Android apps. Sorry but I cannot send you my Public and Private Keys on GitHub. Somebody could take over my names and keys and do some crazy things in my name with it. You can reproduce this bug easy with every Heltec V3.2 or Heltec V4. Von: Garth Vander Houwen Gesendet: Freitag, 9. Januar 2026 10:23 An: meshtastic/Meshtastic-Android ***@***.***> Cc: Ron252525 ***@***.***>; Author ***@***.***> Betreff: Re: [meshtastic/Meshtastic-Android] [Bug]: Regression: Public Key Mismatch Issue reappeared with Heltec Node V3.2 and V4 on latest Android (2.7.10) and iOS (2.7.6) apps (Issue #4144) <https://avatars.githubusercontent.com/u/1795163?s=20&v=4> garthvh left a comment (meshtastic/Meshtastic-Android#4144) <#4144 (comment)> "show both setups next to each other with their keys being incorrect" - Keys are correct but the key-session-number (n+1) must be wrong There is no session number involved in messaging — Reply to this email directly, view it on GitHub <#4144 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/B4MRDBWHEBCKLLUKALPYZFT4F5XPJAVCNFSM6AAAAACQ25QLCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRYGAZTAMJZGQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/B4MRDBVVTRC623QXDFOEFUD4F5XPJA5CNFSM6AAAAACQ25QLCSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTW6GU47E.gif> Message ID: ***@***.*** ***@***.***> >

[Ron252525]

I will wait now with this in mesh blocked V4 node 31 Days long, till my MAC Address will be erased automatically from all DBs in mesh and then retest it and send you the pics you asked for with blurred partly keys.