Android应用仅在启动时注册Geofence，避免切换标签重复触发通知

Hey there! I’ve run into this exact geofence duplication issue before, so let’s break down how to fix it. The core problem here is that your Map Activity is re-registering geofences every time you navigate back to it—either from the nav bar or another screen. Here are practical, actionable solutions to ensure geofences are only registered once per app session (or even persist across app restarts):

1. Use a Global State Flag in Your Application Class #

The Application class’s lifecycle matches your app’s entire runtime, making it perfect for tracking whether geofences have already been registered.

• First, create a custom Application subclass:

  class MyApp : Application() {
      var isGeofenceRegistered = false
      
      override fun onCreate() {
          super.onCreate()
          // Initialize other app-wide setup here
      }
  }
  

  Don’t forget to declare this in your AndroidManifest.xml:

  <application
      android:name=".MyApp"
      ...>
      <!-- Activities, services, etc. -->
  </application>
  

• In your Map Activity, check this flag before registering geofences:

  val myApp = application as MyApp
  if (!myApp.isGeofenceRegistered) {
      // Fetch coordinates from Firebase and register geofences
      registerGeofencesFromFirebase()
      // Mark as registered once successful
      myApp.isGeofenceRegistered = true
  }
  

2. Persist State with SharedPreferences (For App Restarts) #

If you want to avoid re-registering geofences even after the app is killed and restarted, use SharedPreferences to persist the registration state.

• Modify your registration logic to check and update the persisted flag:

  val sharedPrefs = getSharedPreferences("GeofencePrefs", MODE_PRIVATE)
  val isRegistered = sharedPrefs.getBoolean("GEOFENCE_REGISTERED", false)
  
  if (!isRegistered) {
      fetchCoordinatesFromFirebase { coordinates ->
          registerGeofence(coordinates) { success ->
              if (success) {
                  sharedPrefs.edit()
                      .putBoolean("GEOFENCE_REGISTERED", true)
                      .apply()
              }
          }
      }
  }
  

3. Move Registration Logic to a One-Time Launch Point #

Instead of handling geofence registration in the Map Activity’s onResume (which triggers every time you return to the screen), move it to a place that only runs once:

• A splash screen Activity that launches when the app starts
• The onCreate method of your custom Application class
• A WorkManager one-time initializer (for more robust background setup)

This way, registration happens once when the app first launches, not every time you switch to the Map tab.

4. Check for Existing Geofences Before Registering #

Android’s GeofencingClient lets you query already registered geofences. Use this to avoid adding duplicates even if your state flags fail:

geofencingClient.getGeofences().addOnSuccessListener { existingGeofences ->
    val targetGeofenceId = "your_unique_geofence_request_id"
    val geofenceExists = existingGeofences.any { it.requestId == targetGeofenceId }
    
    if (!geofenceExists) {
        // Proceed with registration
        buildAndRegisterGeofence()
    }
}

Important Notes #

• Geofences can be cleared by the system (e.g., after a device restart, if location services are disabled, or if the app is force-stopped). To handle this, you can:
  • Register a BOOT_COMPLETED broadcast receiver to re-register geofences after a restart
  • Check the registration state when the app comes to the foreground (using ProcessLifecycleOwner for lifecycle awareness)
• Always make sure to unregister geofences when they’re no longer needed (e.g., when the user logs out) to avoid unnecessary battery drain.

内容的提问来源于stack exchange，提问作者Alvin Lau