[DO NOT REVIEW][epskc] demo version impl for epskc

[wgtdkp]

No description provided.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.92%. Comparing base (79d1ddc) to head (9bb7a83).
Report is 5 commits behind head on main.

❗ Current head 9bb7a83 differs from pull request most recent head f3d2398

Please upload reports for the commit f3d2398 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #261      +/-   ##
==========================================
+ Coverage   72.88%   72.92%   +0.04%     
==========================================
  Files          72       72              
  Lines        7500     7482      -18     
==========================================
- Hits         5466     5456      -10     
+ Misses       2034     2026       -8     

see 4 files with indirect coverage changes

[wgtdkp]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip.
Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

[Cristib05]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

[wgtdkp]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.

Or, you can patch this PR and follow the guide to build the app on your own.

[Cristib05]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.

Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app.
commissioner_logcat.txt

[wgtdkp]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.
Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app. commissioner_logcat.txt

Thanks for the log. The crash is because your border router doesn't include a id TXT record in its mdns service. If you are using ot-br-psoix for your BR, you probably need to update your code to the latest version.

I should tolerate such issues in the demo app, but without the id of the BR, the demo won't work end to end.

[Cristib05]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.
Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app. commissioner_logcat.txt

Thanks for the log. The crash is because your border router doesn't include a id TXT record in its mdns service. If you are using ot-br-psoix for your BR, you probably need to update your code to the latest version.

I should tolerate such issues in the demo app, but without the id of the BR, the demo won't work end to end.

Thanks for your help! I will update and have another try.

[Cristib05]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.
Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app. commissioner_logcat.txt

Thanks for the log. The crash is because your border router doesn't include a id TXT record in its mdns service. If you are using ot-br-psoix for your BR, you probably need to update your code to the latest version.
I should tolerate such issues in the demo app, but without the id of the BR, the demo won't work end to end.

Thanks for your help! I will update and have another try.

Hi @wgtdkp. I have included the id TXT field and I was able to perform the demo, I was able to see the message which indicated that dataset was saved in Google Play Services. I have another question, I always get an error, Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68. This happens when response to PTR query _meshcop._udp includes in additional section an AAAA record which contains link-local address. If I remove this link-local from additional section, and I only let global ipv6 address, no errors are shown.

I searched for the error message, and I've seen that the issue might be located here

[wgtdkp]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.
Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app. commissioner_logcat.txt

Thanks for the log. The crash is because your border router doesn't include a id TXT record in its mdns service. If you are using ot-br-psoix for your BR, you probably need to update your code to the latest version.
I should tolerate such issues in the demo app, but without the id of the BR, the demo won't work end to end.

Thanks for your help! I will update and have another try.

Hi @wgtdkp. I have included the id TXT field and I was able to perform the demo, I was able to see the message which indicated that dataset was saved in Google Play Services. I have another question, I always get an error, Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68. This happens when response to PTR query _meshcop._udp includes in additional section an AAAA record which contains link-local address. If I remove this link-local from additional section, and I only let global ipv6 address, no errors are shown.

I searched for the error message, and I've seen that the issue might be located here

Can you share the full log of this one "Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68"? It works only if the scope id is appended to the link-local IPv6 address

And what's your Android OS version?

[Cristib05]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.
Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app. commissioner_logcat.txt

Thanks for the log. The crash is because your border router doesn't include a id TXT record in its mdns service. If you are using ot-br-psoix for your BR, you probably need to update your code to the latest version.
I should tolerate such issues in the demo app, but without the id of the BR, the demo won't work end to end.

Thanks for your help! I will update and have another try.

Hi @wgtdkp. I have included the id TXT field and I was able to perform the demo, I was able to see the message which indicated that dataset was saved in Google Play Services. I have another question, I always get an error, Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68. This happens when response to PTR query _meshcop._udp includes in additional section an AAAA record which contains link-local address. If I remove this link-local from additional section, and I only let global ipv6 address, no errors are shown.
I searched for the error message, and I've seen that the issue might be located here

Can you share the full log of this one "Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68"? It works only if the scope id is appended to the link-local IPv6 address

And what's your Android OS version?

Hello, I have attached the log when our BR adds the link local ipv6 adrress in additional data section.
logcat_link-local.txt
For test, I only have Android 10&11 versions.

[wgtdkp]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.
Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app. commissioner_logcat.txt

Thanks for the log. The crash is because your border router doesn't include a id TXT record in its mdns service. If you are using ot-br-psoix for your BR, you probably need to update your code to the latest version.
I should tolerate such issues in the demo app, but without the id of the BR, the demo won't work end to end.

Thanks for your help! I will update and have another try.

Hi @wgtdkp. I have included the id TXT field and I was able to perform the demo, I was able to see the message which indicated that dataset was saved in Google Play Services. I have another question, I always get an error, Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68. This happens when response to PTR query _meshcop._udp includes in additional section an AAAA record which contains link-local address. If I remove this link-local from additional section, and I only let global ipv6 address, no errors are shown.
I searched for the error message, and I've seen that the issue might be located here

Can you share the full log of this one "Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68"? It works only if the scope id is appended to the link-local IPv6 address
And what's your Android OS version?

Hello, I have attached the log when our BR adds the link local ipv6 adrress in additional data section. logcat_link-local.txt For test, I only have Android 10&11 versions.

@Cristib05 Thanks for the bugreport, it's indeed the missing scope ID issue I suspected. I created a new version the APK with the fix. Can you help validate it?
epskc-commissioner-app-debug-fix-lla.zip

[Cristib05]

Here is an the Android APK prebuilt with the ePSKc support: epskc-commissioner-app-debug.apk.zip. Instead of building from source code, you can download the install the APK to reproduce the latest ePSKc demo.

@jwhui In case this can ease Thread Group members' adoption.

Hi @wgtdkp. We have tested this application and we have noticed the application crashes when we try to obtain the dataset. Can you please share an apk with the latest code? I've noticed you have updated this PR since you have shared the initial APK. With ot-cli commissioner everything seems to work fine. Thanks!

Hi, I am out of office before next week. I can help only after next Monday. If will be very helpful if you could upload an Android bugreport when the crash happened.
Or, you can patch this PR and follow the guide to build the app on your own.

Hello @wgtdkp, I have attached a logcat from the app. commissioner_logcat.txt

Thanks for the log. The crash is because your border router doesn't include a id TXT record in its mdns service. If you are using ot-br-psoix for your BR, you probably need to update your code to the latest version.
I should tolerate such issues in the demo app, but without the id of the BR, the demo won't work end to end.

Thanks for your help! I will update and have another try.

Hi @wgtdkp. I have included the id TXT field and I was able to perform the demo, I was able to see the message which indicated that dataset was saved in Google Play Services. I have another question, I always get an error, Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68. This happens when response to PTR query _meshcop._udp includes in additional section an AAAA record which contains link-local address. If I remove this link-local from additional section, and I only let global ipv6 address, no errors are shown.
I searched for the error message, and I've seen that the issue might be located here

Can you share the full log of this one "Failed to connect to Border Router: IO_ERROR: connect socket to peer addr = fe80::.... port = 49155 failed=-68"? It works only if the scope id is appended to the link-local IPv6 address
And what's your Android OS version?

Hello, I have attached the log when our BR adds the link local ipv6 adrress in additional data section. logcat_link-local.txt For test, I only have Android 10&11 versions.

@Cristib05 Thanks for the bugreport, it's indeed the missing scope ID issue I suspected. I created a new version the APK with the fix. Can you help validate it? epskc-commissioner-app-debug-fix-lla.zip

@wgtdkp I have tested with your new .apk file. I could see that now scope id is shown [fe80::...../%wlan0] for example. Dataset was retrieved and saved in google play services. Thanks for providing this update.
Is there any possibility to see the retrieved dataset? Or this would be a security vulnerability?

[wgtdkp]

Is there any possibility to see the retrieved dataset? Or this would be a security vulnerability?

I added a "Show Dataset" button there to display the dataset.
epskc-commissioner-app-debug-show-dataset.zip

[Cristib05]

Is there any possibility to see the retrieved dataset? Or this would be a security vulnerability?

I added a "Show Dataset" button there to display the dataset. epskc-commissioner-app-debug-show-dataset.zip

Thanks for this update! It will be useful for testing purposes. Couple of nits I've found after the last updates (maybe from my older Android version, I don't know.)

1. The list in which border routers are shown has increased its length, even though it's displaying only one border router (initially its length seemed to be dynamically adjusted based on number of elements displayed)
2. The input box for ephemeral key has now a width of only two digits. Every new entered digit is displayed, the previous one seems to be shifted to left side.
   Apart from those, everything seems to be fine. Thanks again for your support!

[wgtdkp]

Is there any possibility to see the retrieved dataset? Or this would be a security vulnerability?

I added a "Show Dataset" button there to display the dataset. epskc-commissioner-app-debug-show-dataset.zip

Thanks for this update! It will be useful for testing purposes. Couple of nits I've found after the last updates (maybe from my older Android version, I don't know.)

1. The list in which border routers are shown has increased its length, even though it's displaying only one border router (initially its length seemed to be dynamically adjusted based on number of elements displayed)
2. The input box for ephemeral key has now a width of only two digits. Every new entered digit is displayed, the previous one seems to be shifted to left side.
   Apart from those, everything seems to be fine. Thanks again for your support!

Could you provide screenshots for the two issues?

[Cristib05]

Is there any possibility to see the retrieved dataset? Or this would be a security vulnerability?

I added a "Show Dataset" button there to display the dataset. epskc-commissioner-app-debug-show-dataset.zip

Thanks for this update! It will be useful for testing purposes. Couple of nits I've found after the last updates (maybe from my older Android version, I don't know.)

1. The list in which border routers are shown has increased its length, even though it's displaying only one border router (initially its length seemed to be dynamically adjusted based on number of elements displayed)
2. The input box for ephemeral key has now a width of only two digits. Every new entered digit is displayed, the previous one seems to be shifted to left side.
   Apart from those, everything seems to be fine. Thanks again for your support!

Could you provide screenshots for the two issues?

commissioner-ss.zip