Google Api Client sometime NULL in onConnected

折月煮酒 提交于 2019-11-30 16:31:50

问题


I implement GoogleApiClient as bellow:

 mGoogleApiClient = new GoogleApiClient.Builder(this)
                .enableAutoManage(this, 0 /* clientId */, this)
                .addApi(LocationServices.API)
                .addApi(Places.GEO_DATA_API)
                .addConnectionCallbacks(this)
                .build();

But in onConnected method I check mGoogleApiClient => value null. In this case I try to re-build googleApiClient but I get error:

  java.lang.IllegalStateException: Already managing a GoogleApiClient with id 0

Please help me understand why mGoogleApiClient is sometimes NULL althought it's connected :|. (Notes. I checked all source code, I never set GoogleApiClient to NULL).

Thanks!

Update

My problem now solved after I try use latest version of play-service.

Thanks everybody for help.


回答1:


I had the same problem. All I did to solve it is remove .enableAutoManage(this, 0 /* clientId */, this) because it just doesn't work properly from what I assumed. Then, override these methods in your activity:

@Override
public void onStart() {
    super.onStart();
    if (mGoogleApiClient != null) {
        mGoogleApiClient.connect();
    }
}

@Override
public void onStop() {
    if (mGoogleApiClient != null && mGoogleApiClient.isConnected()) {
        mGoogleApiClient.disconnect();
    }
    super.onStop();
}

Technically, that is what .enableAutoManage(this, 0 /* clientId */, this) was supposed to do, except that now, everything works as it should.




回答2:


Documentation says: At any given time, only one auto-managed client is allowed per id. To reuse an id you must first call stopAutoManage(FragmentActivity) on the previous client.

What I personally do is making a call to bellow method before I leave the activity, in which I am using the Google Api Client.

private void stopAutoManage() {
    if (mGoogleApiClient != null)
        mGoogleApiClient.stopAutoManage(mActivity);
}



回答3:


I think you'd better watch this reference.

reference page of "public GoogleApiClient.Builder enableAutoManage"

In this page shows that, through IllegalStateException if clientId is already being auto-managed. So, check on your code with

                .enableAutoManage(this, 0 /* clientId */, this)

I think if exception on your code, it could return zero as not completed.




回答4:


If u are facing this problem when u try to reinitialize mGoogleApiClient, then just remove

.enableAutoManage(this, 0 /* clientId */, this)

Use

mGoogleApiClient = new GoogleApiClient.Builder(this)
            .addApi(LocationServices.API)
            .addApi(Places.GEO_DATA_API)
            .addConnectionCallbacks(this)
            .build();

and it will work fine




回答5:


I had the same problem (Already managing a GoogleApiClient with id 0) in a fragment, and finally I resolved it :

  • Override onStart() and onStop() normally
  • Add in onStop() call yourApiGoogle.stopAutoManage(context);

Have a nice day...




回答6:


build() calls onConnected immediately if you are already connected. Therefore, your variable might be null.

Better use

mGoogleApiClient = new GoogleApiClient.Builder(this)
            .enableAutoManage(this, 0 /* clientId */, this)
            .addApi(LocationServices.API)
            .addApi(Places.GEO_DATA_API)
            .addConnectionCallbacks(this);
mGoogleApiClient.build();


来源:https://stackoverflow.com/questions/29619208/google-api-client-sometime-null-in-onconnected

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!