如何强制FusedLocationProviderClient主动请求新位置？升级后无法获取新位置

Hey there, let's figure out why your FusedLocationProviderClient isn't grabbing new locations after you upgraded it. I've run into similar snags before, so let's break down the most likely culprits and fixes:

1. Your LocationRequest has a critical parameter misconfiguration #

Looking at your code snippet, the setExpirationDuration(0) line is a big red flag. Setting the expiration duration to 0 tells the system the location request is immediately expired—so it never even tries to fetch a fresh location!

Fix this by setting a reasonable expiration window that gives the system time to acquire a new fix, like:

.setExpirationDuration(30 * DateUtils.SECOND_IN_MILLIS)

Your setMaxWaitTime(10*DateUtils.SECOND_IN_MILLIS) is fine for aggregating location data, but it can't do anything if the request expires instantly.

2. Double-check runtime permissions #

Since you're using PRIORITY_HIGH_ACCURACY, your app needs the ACCESS_FINE_LOCATION permission. Even if you had it working before, upgrade changes sometimes mess up permission flow:

• Verify you've declared the permission in your AndroidManifest.xml:

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

• Make sure you're requesting and checking runtime permission before initiating the location request:

  if (ContextCompat.checkSelfPermission(this, Manifest.permission.ACCESS_FINE_LOCATION)
          != PackageManager.PERMISSION_GRANTED) {
      // Request permission via ActivityResultContracts here
      return;
  }
  

3. Validate your LocationCallback implementation #

It's easy to miss issues in the callback that make it seem like no location is coming in:

• Ensure you're properly handling the LocationResult in your callback, and checking for non-null locations:

  LocationCallback locationCallback = new LocationCallback() {
      @Override
      public void onLocationResult(LocationResult locationResult) {
          super.onLocationResult(locationResult);
          if (locationResult == null || locationResult.getLocations().isEmpty()) {
              // Fallback to lastLocation if needed, or log an error
              return;
          }
          Location freshLocation = locationResult.getLocations().get(0);
          // Process your fresh location here
      }
  };
  

• Don't forget to remove the callback when you're done (e.g., in onStop() or onDestroy()) to avoid memory leaks:

  fusedLocationClient.removeLocationUpdates(locationCallback);
  

4. Check device location settings #

Even if your code is perfect, the user's device settings can block fresh locations:

• PRIORITY_HIGH_ACCURACY requires the device to be in High Accuracy mode (uses GPS, Wi-Fi, and cell towers). If the user has it set to Battery Saving mode, the system won't use GPS, so you might only get cached locations.
• You can use SettingsClient to check if the current location settings match your request, and prompt the user to adjust them if needed.

5. Confirm you're using the latest play-services-location dependency #

Outdated dependencies can cause compatibility issues after upgrades. Make sure your build.gradle has the latest version of the location library:

implementation 'com.google.android.gms:play-services-location:21.0.1'

Start with fixing the setExpirationDuration parameter first—that's the most likely immediate fix. Then work through the other checks if you still have issues.

内容的提问来源于stack exchange，提问作者Maneki Neko