Non-Proxy node mesh message issues - Android

[BryceCDI]

On the Android version of the application,

Whenever a node is not the proxy node, you are unable to read the proxy state, get the ttl, and refresh the configuration server screen, the app will be stuck on the "refreshing" screen until it ultimately times out.

Steps to reproduce issue

1. provision 2 separate nodes
2. set one of the nodes as the proxy
3. on the node that is not the proxy, click "get ttl" or "read state" buttons in Node configuration screen, or attempt to refresh the Configuration server screen.

Edit - To expand upon this after further testing, it seems as if the "get" mesh messages are being sent, but a status message is not being sent back from the mesh network. My question would be, how would I be able to fix this issue. I have redownloaded the base application from Nordic and it seems to have the same issue.

[Joakim Jakobsen]

Hi. 

Could you add which version of the nRF Mesh app you are using, which phone and which OS version?

Br, 
Joakim

[BryceCDI]

Im using a samsung galaxy tab a - Model num SM-T510

Android Version 10

nRF Mesh app version - 3.1.5

[Joakim Jakobsen]

Thanks.

I'll ask our mobile developers if they have seen something similar, or if they can explain the behavior.

Br, 
Joakim

[BryceCDI]

Has there been any response?

[Joakim Jakobsen]

Working with out developers to test this now. 

Could you also add which FW you are testing this with? Is it a custom application or one of the examples in our nRF5 SDK for Mesh (if yes, which example are you using)?

Br, 
Joakim

[BryceCDI]

i am using a custom FW