Bug in parseMeshPduNotifications

---

Describe the bug parseMeshPduNotifications get stuck in loop if node is not in provisioner’s config: https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library/blob/e03b1eba6cf4d7bb41b1fa36d3ce8055e8df4208/mesh/src/main/java/no/nordicsemi/android/mesh/transport/BaseMeshMessageHandler.java#L113

https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library/blob/e03b1eba6cf4d7bb41b1fa36d3ce8055e8df4208/mesh/src/main/java/no/nordicsemi/android/mesh/transport/BaseMeshMessageHandler.java#L126-L129

I’m not sure exactly what is intended with the while loop logic, for what I can tell it might as well be replaced with while(true), and if the node is not found this will result in an endless loop.

To Reproduce Setup a mesh, Delete node X from mesh Connect to node X as Proxy (whom is not in config anymore) Configure it as Proxy

Device will get stuck in loop of parsing message.

Expected behavior Unsure of expected behavior, since node is not in config, it should probably not be returned but method should anyhow not get stuck.

Platform details:

• Device: Pixel 5
• OS: Android 12L
• Library Version (or Commit) 3.1.6

Logs / Screenshots

12-16 14:17:51.427 24143 24253 V BaseMeshMessageHandler: TTL for received message: 13
12-16 14:17:51.427 24143 24253 V BaseMeshMessageHandler: TTL for received message: 63
12-16 14:17:51.427 24143 24253 V BaseMeshMessageHandler: TTL for received message: 46
12-16 14:17:51.427 24143 24253 V BaseMeshMessageHandler: TTL for received message: 6
12-16 14:17:51.427 24143 24253 V BaseMeshMessageHandler: TTL for received message: 125
12-16 14:17:51.427 24143 24253 V BaseMeshMessageHandler: TTL for received message: 43
... # About 40000 lines of same print
12-16 14:18:27.592 24330 24377 V BaseMeshMessageHandler: TTL for received message: 44
12-16 14:18:27.592 24330 24377 V BaseMeshMessageHandler: TTL for received message: 10
12-16 14:18:27.593 24330 24377 V BaseMeshMessageHandler: TTL for received message: 50
12-16 14:18:27.593 24330 24377 V BaseMeshMessageHandler: Sequence number of received access message: 3756400

[Rawa]

Yes, I tested as mentioned before, this seems like it has resolved it. Not sure if you’ve added some comment if it fails to decode? Would it be possible to get a release out soon this and the other new fixes?

[Itxupengfei]

thank you!