最终的OkHttpClient客户端=new OkHttpClient（）的多线程问题；

Question

package ******;

import android.util.Log;
import android.widget.Toast;

import com.google.firebase.iid.FirebaseInstanceId;
import com.google.firebase.iid.FirebaseInstanceIdService;

import java.io.IOException;

import okhttp3.FormBody;
import okhttp3.OkHttpClient;
import okhttp3.Request;
import okhttp3.RequestBody;

public class MyFirebaseInstanceIDService extends FirebaseInstanceIdService {
    private static final String TAG =   
        MyFirebaseInstanceIDService.class.getSimpleName();

    @Override
    public void onTokenRefresh() {
        // Get updated InstanceID token.
        String token = FirebaseInstanceId.getInstance().getToken();
        sendToken(token);
    }

    private void sendToken(String token) {
        final OkHttpClient client = new OkHttpClient();
        RequestBody body = new FormBody.Builder()
                .add("token",token)
                .build();

        final okhttp3.Request request = new okhttp3.Request.Builder()
                .url("******")
                .post(body)
                .build();

        final Thread thread = new Thread(new Runnable() {
            @Override
            public void run() {
                try {
                    client.newCall(request).execute();
                } catch (IOException e) {
                    e.printStackTrace();
                }
            }
        }); 
    }
}

斯塔克特莱斯

01-26 05:16:09.564: W/GLSUser(2025): [AppCertManager] IOException while 

请求密钥：01-26 05:16:09.564:W/glsuser(2025):java.io.ioException：无效的设备密钥响应。01-26 05:16:09.564:W/Glsuser(2025):at

eka.a(:com.google.android.gms:271)
01-26 05:16:09.564: W/GLSUser(2025):        
eka.a(:com.google.android.gms:4236)
01-26 05:16:09.564: W/GLSUser(2025): at ejz.a(:com.google.android.gms:46)
01-26 05:16:09.564: W/GLSUser(2025): at ejt.a(:com.google.android.gms:53)
01-26 05:16:09.564: W/GLSUser(2025): at ejs.a(:com.google.android.gms:111)
01-26 05:16:09.564: W/GLSUser(2025):at                                                                                                  com.google.android.gms.auth.account.be.
legacy.AuthCronChimeraService.b
(:com.google.android.gms:4052)
01-26 05:16:09.564: W/GLSUser(2025):atdup.call(:com.google.android.gms:2043)
01-26 05:16:09.564: W/GLSUser(2025):a      
java.util.concurrent.FutureTask.run(FutureTask.java:237)

01-26 05:16:09.564:W/glsuser(2025):at kmo.run(:com.google.android.gms:450)01-26 05:16:09.564:W/glsuser(2025):at java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1133)01-26 05:16:09.564:W/glsuser(2025):at java.util.concurrent.threadpoolexecutor$worker.run ID.gms:17)01-26 05:16:09.564:W/glsuser(2025):at java.lang.thread.run(thread.java:761)01-26 05:16:09.572:W/ContentTaskController(2025):向StartTracking提供了无效的newTask。

Answer 1

首先，添加一些日志记录，以便更好地了解发生了什么。例如，你曾经从Firebase得到过令牌吗？我怀疑不是。

其次，不要创建自己的线程实例来使用OKHTTP进行异步调用，检查out.enqueue(...callback..)[请参阅OKHTTP。

然而，在这种特殊情况下，我建议创建一个单独的IntentService来将Firebase令牌发送到服务器。这将调用持续时间、错误处理等从系统调用中分离到ontokenRefresh()。在IntentServiceonhandleIntent()中，可以使用OKHTTP进行同步调用。保持一切美好和简单。