[BUG] Commissioning android tv-app fails: tv-app can't be discovered

[JelenaZdr]

Reproduction steps

The platform app is initiated on the phone, while the chip tool is launched on the computer running Ubuntu 20. However, during commissioning (command: pairing code ), the chip tool fails to discovered the platform app. This issue persists even when utilizing a third-party controller.

Bug prevalence

Whenever i do this

GitHub hash of the SDK that was being used

bcebbc6

Platform

android

Platform Version(s)

No response

Anything else?

bug_no_advertising_tv_app_android.txt

[xvortep]

@bzbarsky-apple @andy31415 @yunhanw-google @tennessee-google Hi, can you please take a look at this? This is a serious blocker for us. Thank you.

[sharadb-amazon]

Is operational discovery (service type: _matter._tcp) failing or something else? Can you attach logs from both the tv-app as well as the chip-tool?

Also, can you use any third-party discovery tool (like "Discovery" app for iOS/MacOS or "Service Browser" for Android to see if the above service type can be discovered using them? Or test using the dns-sd / avahi CLI commands?

[JelenaZdr]

Hello, atteched are the logs from both application.

Also, we tried using a thrid-parthy controller and had the same problem

logChipTool.txt
logTV.txt

[bzbarsky-apple]

That last logTV.txt: I don't see it ever trying to advertise anything with CM=1.

Which means it does not have a commissioning window open, so of course commissioning it will not work.

[xvortep]

Do you know what could be a problem here? Do we have to manually open the commissioning window, or are there some errors that prevent the app to do that automatically?
If there's a problem with DNS implementation used in this app, we could try changing it to "minimal". Do you think that's a good idea?

Thanks!