Xamarin Essentials：Pixel 3上Connectivity.NetworkAccess返回值异常咨询

First off, this isn't a bug in your code—it's a specific edge case tied to how Google Fi and Google VPN interact with Android's connectivity stack. Let's unpack what's happening:

Is this expected behavior? #

Sort of, but it's definitely counterintuitive. Here's why:

• Google Fi uses a unique network architecture that sometimes maintains low-level "always-on" connections (even when mobile data/Wi-Fi are toggled off) for features like Wi-Fi calling, seamless network switching, or Fi's own service syncing.
• When Google VPN is active, it can further mask or override the system's network profile detection. In your case, the system reports NetworkAccess.Internet because the VPN tunnel is technically still active (even without an underlying Wi-Fi/mobile data link), but it can't properly identify the connection type, hence ConnectionProfile.Unknown.

So while this isn't "standard" expected behavior for most devices, it's a known quirk in Google Fi + VPN setups.

Should you combine Connectivity.ConnectionProfiles and Connectivity.NetworkAccess? #

Absolutely. Relying solely on NetworkAccess is risky in edge cases like this. A more robust check would verify two things:

1. NetworkAccess is indeed Internet
2. The ConnectionProfiles list includes at least one valid, non-unknown connection type (like WiFi or Cellular)

Here's how you could adjust your IsConnected function to handle this:

private bool IsConnected() { 
    if (DeviceInfo.DeviceType == DeviceType.Unknown) return false; 

    var currentAccess = Connectivity.NetworkAccess;
    var validProfiles = Connectivity.ConnectionProfiles
        .Any(p => p == ConnectionProfile.WiFi || p == ConnectionProfile.Cellular);

    // Only return true if we have Internet access AND a valid, known connection profile
    return currentAccess == NetworkAccess.Internet && validProfiles;
}

This way, you'll avoid false positives from scenarios where the system reports "Internet access" but can't identify a real, usable connection profile (like your Google Fi + VPN case).

Extra tips #

• If you need even stricter validation, you could add a quick ping to a reliable endpoint (like 8.8.8.8) to confirm actual connectivity—though this adds latency and requires permissions.
• Keep in mind that Google Fi's behavior might change with OS updates or Fi app versions, so testing on the latest software is a good idea.

内容的提问来源于stack exchange，提问作者Dylan McCurry