[iOS] Build fails with "no such module 'MediaPipeTasksVision'" - CocoaPods dependency missing

[coachdap]

[iOS] Build fails with "no such module 'MediaPipeTasksVision'" - CocoaPods dependency missing

Environment:

• Package version: @thinksys/react-native-mediapipe@0.0.19
• Expo SDK: 54
• React Native: 0.81.5
• Platform: iOS
• Build environment: Both local (Xcode 26.3, CocoaPods 1.16.2) and EAS cloud

Issue:
iOS builds are failing with the error:
no such module 'MediaPipeTasksVision'

This started occurring on March 21, 2026, despite no changes to code or dependencies. The app built successfully multiple times throughout February and March 2026 with the exact same configuration.

Root Cause:
The MediaPipeTasksVision dependency appears to no longer produce a usable Swift module during build. While CocoaPods resolves the dependency, the module cannot be imported at compile time (no such module 'MediaPipeTasksVision').

This may be due to upstream changes in how MediaPipe distributes iOS binaries (e.g., XCFramework migration or removal from CocoaPods), or compatibility issues with newer Xcode versions.

$ pod search MediaPipeTasksVision
[!] Unable to find a pod with name, author, summary, or description matching `MediaPipeTasksVision`
However, the package's ThinkSysRNMediapipe.podspec declares:

ruby
s.dependency "MediaPipeTasksVision"
It appears Google removed or changed the distribution method for MediaPipeTasksVision from the CocoaPods trunk repository sometime after March 20, 2026.

Expected Behavior: The package should build successfully on iOS as it did previously.

Actual Behavior: Pod installation succeeds, but the Swift compiler cannot find the MediaPipeTasksVision module during the build phase.

Possible Solutions:

Update the package to use Google's new MediaPipe distribution method (if they changed it)
Pin to a specific MediaPipeTasksVision version that's still available
Bundle the MediaPipe framework directly with the package
Provide migration guide to an alternative pose detection solution
Additional Context: This is blocking production deployments for apps using this package. Any guidance or timeline for a fix would be greatly appreciated.

[tusharthinksys]

Hey @coachdap, thanks for the detailed report — we investigated this thoroughly and here's exactly what's happening.

What's Actually Going On

MediaPipeTasksVision is no longer searchable on CocoaPods Trunk (the publish server), which is why pod search MediaPipeTasksVision returns nothing. However, the pod spec is still available on the CocoaPods CDN (served via jsDelivr), which is a separate read layer that pod install uses.

There are two distinct CocoaPods layers:

• Trunk → the publish/authentication server → pod search hits this → currently broken for MediaPipe
• CDN (cdn.cocoapods.org → jsDelivr) → the download/fetch layer → pod install hits this → still working

The old podspec for MediaPipeTasksVision is still sitting on jsDelivr from when Google originally published it. It was never deleted — only the ability to publish new versions via Trunk is gone.

Why Your Build Is Failing

Your specific environment is likely hitting one of these scenarios:

1. Corporate firewall or network policy blocking requests to cdn.jsdelivr.net or cdn.cocoapods.org
2. A CocoaPods version that falls back to Trunk instead of CDN for spec resolution in your setup
3. EAS / CI environment with restricted outbound network access to CDN endpoints

This explains why it fails consistently for you but may work on other machines — it's a network-level CDN reachability issue, not a missing pod issue.

Current Status

We tested this on a clean machine with all local caches wiped (~/Library/Caches/CocoaPods and ~/.cocoapods/repos/trunk both deleted) and pod install succeeds by fetching the spec directly from the CDN. The library builds and runs successfully.

That said, this is not a permanent or fully reliable situation:

• We are locked to the last published version of MediaPipeTasksVision — no updates can be published via CocoaPods going forward
• Any environment that cannot reach jsDelivr will fail, exactly as you're experiencing
• CocoaPods itself is going read-only on December 2, 2026, after which the CDN's continued availability depends entirely on jsDelivr

What You Can Do Right Now

To unblock your build immediately, add an explicit CDN source at the top of your Podfile:

source 'https://cdn.cocoapods.org/'

Or switch to the GitHub-backed spec repo directly:

source 'https://github.com/CocoaPods/Specs.git'

Our Plan

We are aware this is not a sustainable long-term setup. We are planning to migrate the MediaPipeTasksVision dependency away from CocoaPods Trunk to a direct Git source reference, which will make resolution fully deterministic and independent of Trunk or CDN availability. We'll update this issue once that change is released.

In the meantime please let us know if the CDN source fix above unblocks you. Happy to help debug further if the issue persists in your environment.

[maituanviet-dev]

It's not working, pod can be installed but I cannot build app via Xcode