Net7.0迁移后Xamarin.Android无法捕获Java.Security.Cert.CertificateException

问题分析 #

你在将Xamarin应用从netstandard2.0迁移到.NET 7后，遇到Java.Security.Cert.CertificateException无法被HttpClient.SendAsync的try/catch块捕获的问题。核心原因是：.NET 7的Xamarin.Android中，HttpClientHandler底层依赖Android系统的OkHttp实现，当ServerCertificateCustomValidationCallback返回false时，异常会从Java层抛出并被包装为.NET版的Java.Security.Cert.CertificateException，若未显式捕获该特定异常，可能出现无法拦截的情况；同时Java线程的异常传递机制也可能导致通用Exception捕获失效。

解决方案 #

方案1：显式捕获Java层证书异常 #

修改try/catch块，直接捕获Java.Security.Cert.CertificateException，同时保留通用异常捕获逻辑：

var handler = new HttpClientHandler()
{
    Credentials = Credentials,
    AllowAutoRedirect = false,
    AutomaticDecompression = DecompressionMethods.GZip | DecompressionMethods.Deflate,
    ServerCertificateCustomValidationCallback = OnServerCertificateCustomValidationCallback,
};
var client = new HttpClient(handler);

try
{
    return await httpClient.SendAsync(
        requestMessage, completionOption, cancellationToken);
}
catch (Java.Security.Cert.CertificateException certEx)
{
    // 处理证书验证失败逻辑，如日志记录
    Console.WriteLine($"证书验证失败: {certEx.Message}");
}
catch (Exception e)
{
    // 处理其他类型异常
}

方案2：使用纯.NET实现的SocketsHttpHandler #

替换HttpClientHandler为SocketsHttpHandler，它完全基于.NET runtime实现，不依赖Android系统HTTP客户端，证书验证异常会以标准.NET的HttpRequestException抛出，更符合常规异常捕获逻辑：

var handler = new SocketsHttpHandler()
{
    Credentials = Credentials,
    AllowAutoRedirect = false,
    AutomaticDecompression = DecompressionMethods.GZip | DecompressionMethods.Deflate,
    SslOptions = new SslClientAuthenticationOptions
    {
        RemoteCertificateValidationCallback = (sender, cert, chain, sslPolicyErrors) =>
        {
            // 复用原有验证逻辑
            return OnServerCertificateCustomValidationCallback(sender, cert, chain, sslPolicyErrors);
        }
    }
};
var client = new HttpClient(handler);

try
{
    return await httpClient.SendAsync(requestMessage, completionOption, cancellationToken);
}
catch (HttpRequestException ex)
{
    // 证书验证失败触发此异常，可通过InnerException查看详情
    Console.WriteLine($"请求异常: {ex.Message}");
}
catch (Exception e)
{
    // 处理其他异常
}

关键说明 #

• 方案1适配现有HttpClientHandler使用方式，仅需调整捕获逻辑即可生效；
• 方案2更推荐，它避免了.NET与Java层的交互差异，异常行为与标准.NET保持一致，后续维护更简单。

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