In Android 10 when location is turned on programmatically, I get result code RESULT_CANCELED

Question

In Android 10, when accessing location programmatically, a pop up to turn on location is shown and when pressed ok (i.e. turn on the location) then the callback in onActivityResult where result code I get is Activity.RESULT_CANCELED instead of Activity.RESULT_OK. Also location in the phone is turned on.

This works fine in below Android 10. Only not working in android 10. I get result code this -Activity.RESULT_CANCELED

Enable location code

activity.setFinishOnTouchOutside(true);

    final int REQUEST_LOCATION = 199;

    GoogleApiClient googleApiClient = new GoogleApiClient.Builder(activity)
            .addApi(LocationServices.API)
            .addConnectionCallbacks(new GoogleApiClient.ConnectionCallbacks() {
                @Override
                public void onConnected(Bundle bundle) {
                    Log.e("location", "Connect");
                }

                @Override
                public void onConnectionSuspended(int i) {
                    Log.e("location", "fail");
                    //googleApiClient.connect();
                }
            })
            .addOnConnectionFailedListener(new GoogleApiClient.OnConnectionFailedListener() {
                @Override
                public void onConnectionFailed(ConnectionResult connectionResult) {
                    Log.d("location", "Location error " + connectionResult.getErrorCode());
                }
            }).build();
    googleApiClient.connect();

    LocationRequest locationRequest = LocationRequest.create();
    locationRequest.setPriority(LocationRequest.PRIORITY_HIGH_ACCURACY);
    locationRequest.setInterval(30 * 1000);
    locationRequest.setFastestInterval(5 * 1000);
    LocationSettingsRequest.Builder builder = new LocationSettingsRequest.Builder()
            .addLocationRequest(locationRequest);
    builder.setAlwaysShow(true);

    SettingsClient client = LocationServices.getSettingsClient(activity);
    Task<LocationSettingsResponse> task = client.checkLocationSettings(builder.build());
    task.addOnSuccessListener(activity, new OnSuccessListener<LocationSettingsResponse>() {
        @Override
        public void onSuccess(LocationSettingsResponse locationSettingsResponse) {
            // All location settings are satisfied. The client can initialize
            // location requests here.
            // ...
            Log.d("location_enable", "enable");
        }
    });

    task.addOnFailureListener(activity, new OnFailureListener() {
        @Override
        public void onFailure(@NonNull Exception e) {
            if (e instanceof ResolvableApiException) {
                // Location settings are not satisfied, but this can be fixed
                // by showing the user a dialog.
                try {
                    // Show the dialog by calling startResolutionForResult(),
                    // and check the result in onActivityResult().
                    ResolvableApiException resolvable = (ResolvableApiException) e;
                    resolvable.startResolutionForResult(activity,
                            REQUEST_LOCATION);
                } catch (IntentSender.SendIntentException sendEx) {
                    // Ignore the error.
                }
            }
        }
    });

Get result onActivityResult

@Override
public void onActivityResult(int requestCode, int resultCode, @Nullable Intent data) {
    super.onActivityResult(requestCode, resultCode, data);

    if (requestCode == REQUEST_LOCATION) {
        switch (resultCode) {
            case Activity.RESULT_OK:
                //Success Perform Task Here
                getLocation();
                break;
            case Activity.RESULT_CANCELED:
                progressDialog.dismiss();
                method.alertBox(getResources().getString(R.string.please_allow_location));
                break;
        }
    }
}

AndroidManifest.xml

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

Answer 1

It's a bug and here is the link on google issue tracker https://issuetracker.google.com/issues/140447198

Meanwhile, you can double check the gps status in onActivityResult to workaround this issue in android 10