Android集成Google Cloud PubSub拉取消息时遇gRPC运行时异常

嘿，我看到你在Android Studio 3.0.1上使用Google Cloud PubSub拉取消息时，遇到了io.grpc.StatusRuntimeException: CANCELLED: Failed to read message错误。这个问题通常和gRPC连接稳定性、线程生命周期或者配置细节有关，结合你的代码，我整理了几个针对性的修复方案：

1. 捕获所有异常，排查真实错误原因 #

你的代码目前只捕获了IOException，但gRPC的StatusRuntimeException不属于这个类型，导致你无法看到完整的错误详情。修改doInBackground中的捕获逻辑：

} catch (Exception e) {
    Log.e(TAG, "拉取消息时出错", e); // 用Log.e打印完整异常栈
}

这样能帮你定位到更具体的触发原因，比如权限问题、网络超时或者协议不兼容。

2. 增加gRPC调用超时，避免线程被系统回收 #

AsyncTask的后台线程可能因为系统资源限制被提前终止，导致gRPC调用被取消。给BlockingStub添加超时限制：

import io.grpc.CallOptions;
import java.util.concurrent.TimeUnit;

// ... 初始化Stub的代码修改为：
SubscriberGrpc.SubscriberBlockingStub subscriberBlockingStub = SubscriberGrpc.newBlockingStub(channelImpl)
        .withCallCredentials(MoreCallCredentials.from(credential))
        .withDeadlineAfter(30, TimeUnit.SECONDS); // 设置30秒超时

3. 正确管理ManagedChannel生命周期，避免连接泄漏 #

你的代码没有关闭gRPC通道，这会导致连接资源泄漏，影响后续调用。在doInBackground中添加finally块关闭通道：

@Override
protected Integer doInBackground(String...params){
    ManagedChannel channelImpl = null;
    numMessages = 0; // 初始化默认值
    try{
        Log.d(TAG, "Leyendo archivo de credenciales: "+MainActivity.CREDENTIALS_FILE);
        AssetManager am = context.getAssets();
        InputStream isCredentials = am.open(MainActivity.CREDENTIALS_FILE);
        
        // 初始化通道
        channelImpl = OkHttpChannelBuilder.forAddress("pubsub.googleapis.com",443)
                .negotiationType(NegotiationType.TLS)
                .build();
        Log.d(TAG, "Canal Terminado?:"+ channelImpl.isTerminated());

        GoogleCredentials credential = GoogleCredentials.fromStream(isCredentials);
        credential = credential.createScoped(Arrays.asList("https://www.googleapis.com/auth/pubsub"));

        SubscriberGrpc.SubscriberBlockingStub subscriberBlockingStub = SubscriberGrpc.newBlockingStub(channelImpl)
                .withCallCredentials(MoreCallCredentials.from(credential))
                .withDeadlineAfter(30, TimeUnit.SECONDS); // 添加超时

        PullRequest pullRequest = PullRequest.newBuilder()
                .setSubscription( MainActivity.SUBSCRIPTION )
                .setReturnImmediately( true )
                .setMaxMessages(10)
                .build();

        PullResponse pullResponse = subscriberBlockingStub.pull(pullRequest);
        numMessages = pullResponse.getReceivedMessagesCount();
        Log.d(TAG, "Number of messages received: " + String.valueOf(numMessages));

        for (ReceivedMessage message1 : pullResponse.getReceivedMessagesList()) {
            PubsubMessage pubsubMessage1 = message1.getMessage();
            arrayList.add(pubsubMessage1.toString());
            Log.d(TAG, "Message received (ID="+message1.getAckId()+"): " + pubsubMessage1.toString());
        }
    }catch (Exception e){
        Log.e(TAG, "拉取消息时出错", e);
    } finally {
        // 关闭通道释放资源
        if (channelImpl != null && !channelImpl.isShutdown()) {
            channelImpl.shutdown();
            try {
                channelImpl.awaitTermination(5, TimeUnit.SECONDS);
            } catch (InterruptedException e) {
                Thread.currentThread().interrupt();
            }
        }
    }
    return numMessages; // 返回实际消息数量，而不是固定0
}

同时修改onPostExecute中的Toast，显示正确的消息数：

Toast.makeText(context, "Number of messages received: " + String.valueOf(num) , Toast.LENGTH_LONG).show();

4. 检查网络权限与SSL配置 #

确保你的AndroidManifest.xml中添加了网络权限：

<uses-permission android:name="android.permission.INTERNET" />

如果是Android 7.0+设备，还可以尝试给gRPC通道指定系统默认的SSL上下文，避免证书验证问题：

import javax.net.ssl.SSLContext;
import javax.net.ssl.SSLSocketFactory;
import javax.net.ssl.X509TrustManager;

// ... 初始化通道时修改：
SSLContext sslContext = SSLContext.getDefault();
SSLSocketFactory sslSocketFactory = sslContext.getSocketFactory();
X509TrustManager trustManager = (X509TrustManager) sslContext.getTrustManagers()[0];

ManagedChannel channelImpl = OkHttpChannelBuilder.forAddress("pubsub.googleapis.com",443)
        .negotiationType(NegotiationType.TLS)
        .sslSocketFactory(sslSocketFactory, trustManager)
        .build();

5. 验证服务账号权限 #

确认你的服务账号密钥文件（MainActivity.CREDENTIALS_FILE）对应的账号，在Google Cloud控制台中拥有Pub/Sub订阅者（roles/pubsub.subscriber）权限。可以在IAM页面给该账号添加对应权限。

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