iOS端WhatsApp分享扩展多图分享重复显示最后一张图片问题求助

Hey there, sorry to hear you're stuck with this tricky share extension issue! This is a super common gotcha when dealing with WhatsApp's share flow, since it handles attachment packaging a bit differently than the Photos app or direct app-to-app sharing.

Let's break down why this might be happening, and how to fix it:

• Variable capture bug in async loops: The most likely culprit here is a classic async loop reference issue. If your code loops through attachments and uses an async block (like the DispatchQueue.global one you started with), it’s easy to accidentally reuse the same attachment reference across all iterations. By the time the async task runs, the loop has already finished, so every task ends up pointing to the last attachment in the list.
• WhatsApp’s unique attachment structure: Unlike the Photos app which often passes each image as a separate NSExtensionItem, WhatsApp tends to bundle all shared images into a single NSExtensionItem with multiple attachments. If your code isn’t iterating through these attachments properly (or is overwriting a shared data variable), you’ll end up with duplicates of the last image.

Here’s how to fix this step by step:

1. Fix variable capture in your loop: When processing each attachment, explicitly capture the current attachment inside the loop iteration so each async closure uses its own unique reference. For example:

   DispatchQueue.global(qos: .userInteractive).async { [weak self] in
       guard let self = self else { return }
       guard let inputItem = self.extensionContext?.inputItems.first as? NSExtensionItem else { return }
       guard let attachments = inputItem.attachments as? [NSItemProvider] else { return }
       
       // Loop through each attachment with proper per-iteration capture
       for attachment in attachments {
           // Create a local copy to avoid reference reuse across async tasks
           let currentAttachment = attachment
           currentAttachment.loadObject(ofClass: UIImage.self) { [weak self] (result, error) in
               guard let self = self, let image = result as? UIImage else { return }
               // Now process this image - it should be unique to each attachment
               self.handleSharedImage(image)
           }
       }
   }
   

   Notice the currentAttachment = attachment line inside the loop? This ensures every async task grabs its own distinct attachment reference instead of sharing the loop’s mutable variable.

2. Avoid reusing shared data variables: Double-check that you aren’t using a single UIImage or data variable to load all attachments. Each attachment should be loaded and processed independently, so previous images don’t get overwritten by the last one.

3. Debug with unique identifiers: For quick verification, print out the itemIdentifier of each NSItemProvider in the loop. If WhatsApp is passing unique identifiers for each image, you can confirm the issue is definitely in how you’re capturing or loading the attachments, not in the data itself.

Another small tip: WhatsApp might use non-standard UTIs for images sometimes. You can add a check with hasItemConformingToTypeIdentifier to ensure you’re only loading valid image attachments before processing them.

Give these fixes a shot—this variable capture bug is almost certainly the root cause here!

内容来源于stack exchange