【问题标题】:Is it possible to have multiple GoogleApiClients within one activity?一个活动中是否可以有多个 GoogleApiClients?
【发布时间】:2017-04-06 21:07:48
【问题描述】:

我正在尝试制作一个位置感知的商业搜索应用。为此,我使用 Google Places Api,特别是 Places.GEO_DATA_API 和 LocationServices.API。这个想法是用户可以使用他们当前的位置或使用自动完成搜索来输入地址。我的问题是我认为调用onConnected() 时这两个api 混淆了,因为我不断收到此错误:

E/AndroidRuntime: FATAL EXCEPTION: main
                  Process: edu.depaul.csc472.coffeeshoplocator, PID: 9420
                  java.lang.IllegalStateException: GoogleApiClient is not connected yet.
                      at com.google.android.gms.internal.zzrb.zzb(Unknown Source)
                      at com.google.android.gms.internal.zzrf.zzb(Unknown Source)
                      at com.google.android.gms.internal.zzrd.zzb(Unknown Source)
                      at com.google.android.gms.location.internal.zzd.requestLocationUpdates(Unknown Source)
                      at edu.depaul.csc472.coffeeshoplocator.MainActivity.startLocationUpdates(MainActivity.java:233)
                      at edu.depaul.csc472.coffeeshoplocator.MainActivity.getLocation(MainActivity.java:241)
                      at edu.depaul.csc472.coffeeshoplocator.MainActivity.onConnected(MainActivity.java:263)
                      at com.google.android.gms.common.internal.zzk.zzp(Unknown Source)
                      at com.google.android.gms.internal.zzrd.zzn(Unknown Source)
                      at com.google.android.gms.internal.zzrb.zzass(Unknown Source)
                      at com.google.android.gms.internal.zzrb.onConnected(Unknown Source)
                      at com.google.android.gms.internal.zzrf.onConnected(Unknown Source)
                      at com.google.android.gms.internal.zzqr.onConnected(Unknown Source)
                      at com.google.android.gms.common.internal.zzj$1.onConnected(Unknown Source)
                      at com.google.android.gms.common.internal.zze$zzj.zzavj(Unknown Source)
                      at com.google.android.gms.common.internal.zze$zza.zzc(Unknown Source)
                      at com.google.android.gms.common.internal.zze$zza.zzv(Unknown Source)
                      at com.google.android.gms.common.internal.zze$zze.zzavl(Unknown Source)
                      at com.google.android.gms.common.internal.zze$zzd.handleMessage(Unknown Source)
                      at android.os.Handler.dispatchMessage(Handler.java:102)
                      at android.os.Looper.loop(Looper.java:154)
                      at android.app.ActivityThread.main(ActivityThread.java:6077)
                      at java.lang.reflect.Method.invoke(Native Method)
                      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

它只是偶尔发生。除了这次崩溃之外,我已经成功运行了该程序,没有任何意外行为。

构建api的代码如下:

protected synchronized void buildGoogleApiClient(){
        mGoogleApiLocation = new GoogleApiClient.Builder(this)
                .addConnectionCallbacks(this)
                .addOnConnectionFailedListener(this)
                .addApi(LocationServices.API)
                .build();
         mGoogleApiAutoComplete = new GoogleApiClient.Builder(this)
                 .addApi(Places.GEO_DATA_API)
                 .enableAutoManage(this,GOOGLE_API_CLIENT_ID,this)
                 .addConnectionCallbacks(this)
                 .build();
    }

这是我的onConnected() 方法,它向用户请求访问精细位置的权限,然后尝试获取用户的位置:

@Override
    public void onConnected(Bundle bundle) {
        requestForSpecificPermission();
        getLocation();
        placeArrayAdapter.setGoogleApiClient(mGoogleApiAutoComplete);

    } 

...还有我的getLocation() 方法:

private void getLocation(){
        try {
            location = LocationServices.FusedLocationApi.getLastLocation(mGoogleApiLocation);
            if (location == null) {
                LocationServices.FusedLocationApi.requestLocationUpdates(mGoogleApiLocation, locationRequest, this);
            }
            else{
                handleNewLocation(location);
            }
        }catch (SecurityException e){
            Toast.makeText(getApplicationContext(),
                    "You don't have permission!", Toast.LENGTH_LONG)
                    .show();
        }
    } 

我的好奇心是一:如果根据我的理解你必须连接到电话onConnected(),我怎么会得到这个错误,二:为什么这只发生在某些时候。首先是否允许有多个客户端,或者如果不允许,您如何在同一个活动中使用两种不同的技术 (api)?

【问题讨论】:

    标签: java android google-maps-api-3 google-play-services google-places-api


    【解决方案1】:

    不要在您的Activity/Fragment 中使用implements ConnectionCallbacks 并尝试以下操作:

    GoogleApiClient.ConnectionCallbacks mGoogleApiLocationCallback = new GoogleApiClient.ConnectionCallbacks() {
            @Override
            public void onConnected(@Nullable Bundle bundle) {
    
            }
    
            @Override
            public void onConnectionSuspended(int i) {
    
            }
        };
    
        GoogleApiClient.ConnectionCallbacks mGoogleApiAutoCompleteCallback = new GoogleApiClient.ConnectionCallbacks() {
            @Override
            public void onConnected(@Nullable Bundle bundle) {
    
            }
    
            @Override
            public void onConnectionSuspended(int i) {
    
            }
        };
    

    然后像这样改变你的方法:

    protected synchronized void buildGoogleApiClient(){
        mGoogleApiLocation = new GoogleApiClient.Builder(context)
                .addConnectionCallbacks(mGoogleApiLocationCallback)
                .addOnConnectionFailedListener(this)
                .addApi(LocationServices.API)
                .build();
        mGoogleApiAutoComplete = new GoogleApiClient.Builder(context)
                .addConnectionCallbacks(mGoogleApiAutoCompleteCallback)
                .addApi(Places.GEO_DATA_API)
                .enableAutoManage(this,GOOGLE_API_CLIENT_ID,this)
                .build();
    }
    

    只需确保从您的 Activity/Fragment 中删除 implements GoogleApiClient.ConnectionCallbacks

    【讨论】:

    • 虽然对,但我并不疯狂……这可能就是错误所在。之前这两个 API 之间存在冲突,但您可以拥有多个 API。它不再崩溃,但就像我说的那样,它只是偶尔会崩溃。
    • 如果两个不同的客户端尝试使用相同的回调,这将是一个问题。因此,为每个客户提供完全独立的客户应该可以完成这项工作。偶尔还是很奇怪
    猜你喜欢
    • 2018-10-20
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多