SwiftUI中LocationManager与ViewModel的联动方案咨询

方案一：在View层监听位置变化（最简单直接） #

利用SwiftUI的.onReceive修饰符监听LocationManager的location属性变化，一旦获取到新位置就调用ViewModel的getData方法。这种方式无需修改原有类结构，耦合度低。

修改ShowData视图代码：

struct ShowData: View {
     @StateObject var locationManager = LocationManager()
     @StateObject var viewModel = ViewModel()

     var body: some View {
          // 你的视图内容，比如List(viewModel.dataArray) { ... }
          Text("展示数据")
               .onReceive(locationManager.$location) { newLocation in
                    guard let location = newLocation else { return }
                    viewModel.getData(location: location)
               }
     }
}

方案二：让ViewModel持有LocationManager并监听（更符合MVVM职责） #

将LocationManager的实例交由ViewModel管理，在ViewModel内部订阅位置变化，视图层仅负责展示，逻辑更清晰。

修改ViewModel代码：

class ViewModel: ObservableObject {
    @Published var dataArray = [Model]()
    private let locationManager = LocationManager()
    private var cancellables = Set<AnyCancellable>()

    init() {
        // 订阅location的变化，过滤nil值后调用getData
        locationManager.$location
            .compactMap { $0 }
            .sink { [weak self] location in
                self?.getData(location: location)
            }
            .store(in: &cancellables)
    }

    func getData(location: CLLocation) {
         // 异步API调用逻辑，完成后更新dataArray
         DispatchQueue.global().async {
             // 模拟API请求
             let fetchedData = [Model()]
             DispatchQueue.main.async {
                 self.dataArray = fetchedData
             }
         }
    }
}

修改ShowData视图，仅需初始化ViewModel：

struct ShowData: View {
     @StateObject var viewModel = ViewModel()

     var body: some View {
          // 展示viewModel.dataArray的内容
     }
}

方案三：修复闭包捕获问题（针对你之前的尝试） #

你遇到的"closure capturing a mutating self parameter"问题，通常是闭包强引用self导致循环引用或捕获时机不当。通过弱引用self并调整LocationManager的初始化方式即可解决。

修改LocationManager代码：

final class LocationManager: NSObject, ObservableObject {
    @Published var location: CLLocation?
    private let locationManager = CLLocationManager()
    private var locationUpdateHandler: ((CLLocation) -> Void)?

    // 新增带回调的初始化方法
    init(locationUpdateHandler: @escaping (CLLocation) -> Void) {
        self.locationUpdateHandler = locationUpdateHandler
        super.init()
        setupLocationManager()
    }

    // 保留无参初始化供其他场景使用
    override init() {
        super.init()
        setupLocationManager()
    }

    private func setupLocationManager() {
        locationManager.requestWhenInUseAuthorization()
        locationManager.startUpdatingLocation()
        locationManager.delegate = self
    }
}

extension LocationManager: CLLocationManagerDelegate {
    func locationManager(_ manager: CLLocationManager, didUpdateLocations locations: [CLLocation]) {
        guard let location = locations.last else {
            return
        }
        DispatchQueue.main.async {
            self.location = location
            // 触发回调
            self.locationUpdateHandler?(location)
        }
    }
}

在ViewModel中初始化LocationManager时使用弱引用：

class ViewModel: ObservableObject {
    @Published var dataArray = [Model]()
    private let locationManager: LocationManager

    init() {
        // 用weak self避免循环引用
        self.locationManager = LocationManager { [weak self] location in
            self?.getData(location: location)
        }
    }

    func getData(location: CLLocation) {
         // 异步API调用逻辑
    }
}

注意事项 #

• 方案一适合快速实现，无需改动原有类结构；
• 方案二更贴合MVVM设计，将定位与数据请求逻辑统一放在ViewModel；
• 方案三针对性解决闭包引用问题，核心是通过[weak self]避免循环引用。

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