Android应用首次授予位置权限后崩溃问题求助

这种问题大多和权限回调时机与位置服务初始化的冲突、主线程阻塞或生命周期管理不当有关，以下是针对性的解决方案：

核心排查方向 #

• 权限刚授予时，位置服务客户端未完成初始化就触发请求
• 同步位置请求阻塞主线程导致ANR或崩溃
• 位置回调在组件销毁后仍执行，引发空指针
• 权限状态判断逻辑遗漏了刚授权的边界情况

具体修复步骤 #

1. 延迟初始化位置服务客户端 #

不要在App启动时就初始化FusedLocationProviderClient或LocationManager，而是等权限明确授予后再初始化，避免空指针或未授权状态下的异常：

// Kotlin示例
private var fusedLocationClient: FusedLocationProviderClient? = null
private val LOCATION_PERMISSION_REQUEST = 1001

override fun onRequestPermissionsResult(requestCode: Int, permissions: Array<out String>, grantResults: IntArray) {
    super.onRequestPermissionsResult(requestCode, permissions, grantResults)
    if (requestCode == LOCATION_PERMISSION_REQUEST) {
        if (grantResults.firstOrNull() == PackageManager.PERMISSION_GRANTED) {
            // 权限确认授予后再初始化客户端
            fusedLocationClient = LocationServices.getFusedLocationProviderClient(this)
            startLocationFetch()
        }
    }
}

private fun startLocationFetch() {
    fusedLocationClient?.let { client ->
        val request = LocationRequest.create().apply {
            priority = LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY
            interval = 15000
        }
        val callback = object : LocationCallback() {
            override fun onLocationResult(result: LocationResult) {
                result.lastLocation?.let { loc ->
                    // 处理获取到的位置
                }
            }
        }
        client.requestLocationUpdates(request, callback, Looper.getMainLooper())
    }
}

2. 避免主线程同步执行位置请求 #

如果使用旧的LocationManager，同步获取位置会阻塞主线程，改用子线程或异步API：

// Java示例
private void fetchLocationSafely() {
    LocationManager manager = (LocationManager) getSystemService(Context.LOCATION_SERVICE);
    if (ActivityCompat.checkSelfPermission(this, Manifest.permission.ACCESS_FINE_LOCATION) != PackageManager.PERMISSION_GRANTED) {
        return;
    }

    // 用HandlerThread执行耗时的位置请求
    HandlerThread locationThread = new HandlerThread("LocationFetchThread");
    locationThread.start();
    new Handler(locationThread.getLooper()).post(() -> {
        Location lastLocation = manager.getLastKnownLocation(LocationManager.GPS_PROVIDER);
        // 切回主线程处理结果
        runOnUiThread(() -> {
            if (lastLocation != null) {
                // 更新UI或业务逻辑
            }
        });
        locationThread.quitSafely();
    });
}

3. 严格管理位置回调的生命周期 #

在Activity/Fragment销毁时，必须移除位置回调，防止组件销毁后回调执行引发空指针或内存泄漏：

private var locationCallback: LocationCallback? = null

override fun onDestroy() {
    super.onDestroy()
    fusedLocationClient?.removeLocationUpdates(locationCallback)
    fusedLocationClient = null
    locationCallback = null
}

4. 添加异常捕获，防止崩溃扩散 #

即使权限已经授予，仍可能出现SecurityException或其他意外异常，添加try-catch兜底：

private fun startLocationFetch() {
    try {
        fusedLocationClient?.let { client ->
            // 位置请求逻辑
        }
    } catch (e: SecurityException) {
        Log.e("LocationCrash", "权限校验异常", e)
        // 可选：提示用户重新授权
    } catch (e: Exception) {
        Log.e("LocationCrash", "位置请求失败", e)
    }
}

5. 完善权限状态的二次校验 #

在onResume中再次检查权限状态，处理用户从设置页手动授权的情况，同时避免重复请求：

private var hasFetchedLocation = false

override fun onResume() {
    super.onResume()
    if (ActivityCompat.checkSelfPermission(this, Manifest.permission.ACCESS_FINE_LOCATION) == PackageManager.PERMISSION_GRANTED) {
        if (fusedLocationClient == null) {
            fusedLocationClient = LocationServices.getFusedLocationProviderClient(this)
        }
        if (!hasFetchedLocation) {
            startLocationFetch()
            hasFetchedLocation = true
        }
    } else {
        requestLocationPermission()
    }
}

内容的提问来源于stack exchange，提问作者Jayesh Kumavat