Description
On the WinUI platform, any calls to Connectivity.Current only work from the first thread to access the property. Subsequent calls from any other thread will cause a silent thread access exception:

That will end in a value of Unknown being returned:

Doesn't matter which thread is first - main thread or background thread, it will always return correct value, and continue to return the correct value for that thread. But if you try to access it from a different thread, that is when this issue occurs.
Steps to Reproduce
I've linked to a sample repro below. Just run and click button 1 then button 2, or button 2 then button 1 to invert the outcome.
Main thread before bg thread:

Bg thread before main thread:

Link to public reproduction project repository
https://github.com/breenbob/MauiWindowsConnectivityIssue
Version with bug
6.0.400
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
10.0.17763.0
Did you find any workaround?
If checks are always done on the same thread you won't see the issue, but that's not a feasible long term solution.
Relevant log output
No response
Description
On the WinUI platform, any calls to Connectivity.Current only work from the first thread to access the property. Subsequent calls from any other thread will cause a silent thread access exception:

That will end in a value of Unknown being returned:

Doesn't matter which thread is first - main thread or background thread, it will always return correct value, and continue to return the correct value for that thread. But if you try to access it from a different thread, that is when this issue occurs.
Steps to Reproduce
I've linked to a sample repro below. Just run and click button 1 then button 2, or button 2 then button 1 to invert the outcome.
Main thread before bg thread:

Bg thread before main thread:

Link to public reproduction project repository
https://github.com/breenbob/MauiWindowsConnectivityIssue
Version with bug
6.0.400
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
10.0.17763.0
Did you find any workaround?
If checks are always done on the same thread you won't see the issue, but that's not a feasible long term solution.
Relevant log output
No response