iOS应用每次激活耗大量数据：原因排查与优化咨询

你的核心问题在于当前的图片加载方式没有任何缓存机制，每次Widget刷新都会重新下载所有图片，叠加5个Widget的20-30张图片，就会产生可观的流量消耗。以下是具体的优化方案：

1. 利用URLSession的系统缓存替代Data(contentsOf:) #

Data(contentsOf:)是同步阻塞式请求，且默认不会充分利用iOS的HTTP缓存机制。改用URLSession发起异步请求，系统会自动根据服务器返回的Cache-Control、ETag等响应头进行缓存，避免重复下载未更新的图片。

示例代码：

extension Image {
    static func from(url: URL?) async -> Image {
        guard let url = url else {
            return Image(systemName: "photo.fill")
        }
        
        let urlRequest = URLRequest(url: url)
        do {
            let (data, response) = try await URLSession.shared.data(for: urlRequest)
            guard let httpResponse = response as? HTTPURLResponse, httpResponse.statusCode == 200 else {
                return Image(systemName: "photo.fill")
            }
            if let uiImage = UIImage(data: data) {
                return Image(uiImage: uiImage)
            }
        } catch {
            print("图片加载失败: \(error)")
        }
        return Image(systemName: "photo.fill")
    }
}

在Widget视图中异步加载：

struct WidgetEntryView: View {
    var entry: Provider.Entry
    @State private var loadedImage: Image?

    var body: some View {
        Group {
            if let image = loadedImage {
                image
            } else {
                Image(systemName: "photo.fill")
                    .task {
                        if let url = entry.imageUrl {
                            loadedImage = await Image.from(url: url)
                        }
                    }
            }
        }
    }
}

2. 实现自定义缓存策略（针对无缓存头的服务器） #

如果服务器未配置合适的缓存响应头，可自己实现内存+磁盘的双缓存机制：

• 内存缓存：用NSCache存储常用图片，快速读取
• 磁盘缓存：将图片按URL哈希值命名，存储到应用缓存目录，重启后仍可读取

示例代码：

class ImageCache {
    static let shared = ImageCache()
    
    private let memoryCache = NSCache<NSString, UIImage>()
    private let diskCacheDirectory: URL
    
    private init() {
        let cacheDir = FileManager.default.urls(for: .cachesDirectory, in: .userDomainMask).first!
        diskCacheDirectory = cacheDir.appendingPathComponent("WidgetImageCache")
        try? FileManager.default.createDirectory(at: diskCacheDirectory, withIntermediateDirectories: true)
    }
    
    func image(for url: URL) -> UIImage? {
        let key = url.absoluteString as NSString
        // 优先查内存缓存
        if let image = memoryCache.object(forKey: key) {
            return image
        }
        // 再查磁盘缓存
        let filePath = diskCacheDirectory.appendingPathComponent(key.md5)
        if let data = try? Data(contentsOf: filePath), let image = UIImage(data: data) {
            memoryCache.setObject(image, forKey: key)
            return image
        }
        return nil
    }
    
    func store(image: UIImage, for url: URL) {
        let key = url.absoluteString as NSString
        memoryCache.setObject(image, forKey: key)
        guard let data = image.jpegData(compressionQuality: 0.8) else { return }
        let filePath = diskCacheDirectory.appendingPathComponent(key.md5)
        try? data.write(to: filePath)
    }
}

// 给String添加MD5哈希扩展（需导入CommonCrypto）
extension String {
    var md5: String {
        let data = Data(utf8)
        var digest = [UInt8](repeating: 0, count: Int(CC_MD5_DIGEST_LENGTH))
        _ = data.withUnsafeBytes {
            CC_MD5($0.baseAddress, CC_LONG(data.count), &digest)
        }
        return digest.map { String(format: "%02hhx", $0) }.joined()
    }
}

修改图片加载方法，优先读取缓存：

extension Image {
    static func from(url: URL?) async -> Image {
        guard let url = url else {
            return Image(systemName: "photo.fill")
        }
        
        if let cachedImage = ImageCache.shared.image(for: url) {
            return Image(uiImage: cachedImage)
        }
        
        do {
            let (data, response) = try await URLSession.shared.data(from: url)
            guard let httpResponse = response as? HTTPURLResponse, httpResponse.statusCode == 200 else {
                return Image(systemName: "photo.fill")
            }
            if let uiImage = UIImage(data: data) {
                ImageCache.shared.store(image: uiImage, for: url)
                return Image(uiImage: uiImage)
            }
        } catch {
            print("图片加载失败: \(error)")
        }
        return Image(systemName: "photo.fill")
    }
}

3. 优化Widget刷新触发逻辑 #

避免每次应用激活就刷新Widget，应根据数据更新时机触发：

• 在TimelineProvider的getTimeline(for:completion:)中，设置合理的刷新策略，比如TimelinePolicy.after(nextUpdateDate)，仅在数据可能更新的时间点刷新
• 当应用内数据变化时，通过WidgetCenter.shared.reloadTimelines(ofKind:)主动刷新对应Widget，减少无意义的刷新

4. 图片尺寸适配优化 #

Widget显示空间有限，无需加载原图尺寸。可与后端约定，通过URL参数指定缩略图尺寸（如https://example.com/image.jpg?w=120&h=120），请求适配Widget大小的图片，大幅降低单图体积。

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