SwiftUI WidgetKit中getTimeline被连续多次调用问题求助

问题场景 #

真机运行Widget扩展时，getTimeline函数会被多次调用（3-5次不等）；如果在Task中加入异步网络请求，调用次数会飙升至近20次，最终导致内存耗尽崩溃。

原代码 #

func getTimeline(for configuration: ConfigurationIntent, in context: Context, completion: @escaping (Timeline<Entry>) -> ()) {
    
    print("CALLING getTimeline")
  
    let currentDate = Date()
    let updateDate = Calendar.current.date(byAdding: .hour, value: 5, to: currentDate)!
    
    let entry = SimpleEntry(date: Date(), configuration: configuration, items: DummyData.data)
    let timeline = Timeline(entries: [entry], policy: .after(updateDate))
     
    print("Calling Completion Timeline Discounts ")
    completion(timeline)
}

输出日志 #

Current Date:2023-10-22 23:05:49 +0000 update Date is: 2023-10-23 04:05:49 +0000
Current Date:2023-10-22 23:05:52 +0000 update Date is: 2023-10-23 04:05:52 +0000
Current Date:2023-10-22 23:05:53 +0000 update Date is: 2023-10-23 04:05:53 +0000
Current Date:2023-10-22 23:05:54 +0000 update Date is: 2023-10-23 04:05:54 +0000

CALLING getTimeline
Calling Completion Timeline Discounts 
CALLING getTimeline
Calling Completion Timeline Discounts 
CALLING getTimeline
Calling Completion Timeline Discounts 
CALLING getTimeline
Calling Completion Timeline Discounts 

原因分析 #

1. WidgetKit调度特性：系统会根据屏幕解锁、Widget页面切换、系统资源状态等场景自动触发getTimeline调用，属于框架正常行为，但未管控的重复调用会放大问题。
2. 异步请求无并发控制：每次调用getTimeline都发起新的异步请求，未取消之前未完成的任务，导致大量并发请求堆积，内存占用持续飙升直至崩溃。

解决方案 #

1. 管控并发异步任务 #

在Provider中维护当前异步任务的引用，每次调用getTimeline时取消之前的任务，避免请求堆积。

2. 优化Timeline刷新策略 #

确保updateDate设置合理，避免过于频繁的自动刷新；若无需实时更新，可使用.never策略，仅通过手动刷新触发更新。

3. 缓存请求结果 #

将网络请求结果缓存，重复调用时优先使用缓存，减少不必要的网络请求。

4. 错误回退机制 #

异步请求失败时，使用缓存数据并设置合理的重试间隔，避免无限触发请求。

修改后的代码示例 #

class WidgetProvider: IntentTimelineProvider {
    // 存储当前异步任务，用于取消并发请求
    private var currentFetchTask: Task<Void, Error>?
    
    func getTimeline(for configuration: ConfigurationIntent, in context: Context, completion: @escaping (Timeline<Entry>) -> ()) {
        print("CALLING getTimeline")
        
        // 取消之前未完成的任务，避免请求堆积
        currentFetchTask?.cancel()
        
        currentFetchTask = Task { [weak self] in
            defer { self?.currentFetchTask = nil }
            
            do {
                // 执行异步网络请求
                let fetchedItems = try await fetchRemoteData()
                
                let currentDate = Date()
                let updateDate = Calendar.current.date(byAdding: .hour, value: 5, to: currentDate)!
                let entry = SimpleEntry(date: currentDate, configuration: configuration, items: fetchedItems)
                
                let timeline = Timeline(entries: [entry], policy: .after(updateDate))
                print("Calling Completion Timeline Discounts ")
                completion(timeline)
            } catch {
                // 请求失败时使用缓存数据，5分钟后重试
                let fallbackEntry = SimpleEntry(date: Date(), configuration: configuration, items: DummyData.data)
                let retryDate = Date().addingTimeInterval(300)
                let fallbackTimeline = Timeline(entries: [fallbackEntry], policy: .after(retryDate))
                
                completion(fallbackTimeline)
                print("Request failed, using fallback data")
            }
        }
    }
    
    // 替换为实际网络请求逻辑
    private func fetchRemoteData() async throws -> [Item] {
        try await Task.sleep(nanoseconds: 1_000_000_000)
        return DummyData.data
    }
}

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