pod install cannot download the ffmpeg-kit iOS framework any more
Fix it fast
Most common cause, 1 of 3A dependency still points at the retired ffmpeg-kit pods
Replace the wrapper with a maintained fork from pub.dev or npm, check that its iOS podspec downloads from a live location, then reinstall pods from a clean state.
# Flutter
flutter pub remove ffmpeg_kit_flutter_full_gpl
flutter pub add <maintained_fork_package>
cd ios && rm -rf Pods Podfile.lock && pod install --repo-update
# React Native
npm uninstall ffmpeg-kit-react-native
npm install <maintained-fork>
cd ios && rm -rf Pods Podfile.lock && pod install --repo-updateShort answer
FFmpegKit has been officially retired, and the prebuilt iOS framework zips its podspecs download from GitHub releases now return 404. Every ffmpeg-kit-ios-* pod, including those pulled in by ffmpeg_kit_flutter or ffmpeg-kit-react-native, therefore fails in pod install. Move to a maintained community fork, build FFmpegKitNext from source, or vendor a framework you already have.
Which cause do you have?
Find which pod brings in ffmpeg-kit and try the download yourself. A 404 from GitHub confirms the binaries are gone, not that your network is broken.
grep -n "ffmpeg-kit" ios/Podfile.lock
curl -f -sS -L -o /dev/null https://github.com/arthenica/ffmpeg-kit/releases/download/v6.0/ffmpeg-kit-full-gpl-6.0-ios-xcframework.zipThen find the line you see in this list and open its fix:
- 1A dependency still points at the retired ffmpeg-kit pods
Podfile.lock lists ffmpeg-kit-ios-min, -https, -full or -full-gpl at version 6.0 or 6.0.LTS - 2You want the maintained continuation, which ships no binaries
You prefer the original author's code line over a community fork - 3You already have a working copy of the frameworks
An older checkout, CI cache or Pods folder still contains the ffmpegkit .xcframework bundles
What does the error look like?
[!] Error installing ffmpeg-kit-ios-full-gplcurl: (22) The requested URL returned error: 404curl: (56) The requested URL returned error: 404
Cause 1 of 3
A dependency still points at the retired ffmpeg-kit pods
You seePodfile.lock lists ffmpeg-kit-ios-min, -https, -full or -full-gpl at version 6.0 or 6.0.LTS
Check
The FFmpegKit README states the project is officially retired and points to community forks for Android, Flutter and React Native. The wrapper packages declare these iOS pods as dependencies, so the failure appears even if your app never names ffmpeg-kit directly.
grep -rn "ffmpeg_kit\|ffmpeg-kit" pubspec.yaml package.json ios/Podfile 2>/dev/nullFix
Replace the wrapper with a maintained fork from pub.dev or npm, check that its iOS podspec downloads from a live location, then reinstall pods from a clean state.
# Flutter
flutter pub remove ffmpeg_kit_flutter_full_gpl
flutter pub add <maintained_fork_package>
cd ios && rm -rf Pods Podfile.lock && pod install --repo-update
# React Native
npm uninstall ffmpeg-kit-react-native
npm install <maintained-fork>
cd ios && rm -rf Pods Podfile.lock && pod install --repo-updateVerify
pod install finishes and the build links without ffmpeg-kit-ios-* in Podfile.lock.
grep -c 'ffmpeg-kit-ios' ios/Podfile.lockConfirmed by raw.githubusercontent.com
Cause 2 of 3
You want the maintained continuation, which ships no binaries
You seeYou prefer the original author's code line over a community fork
Check
FFmpegKitNext is described as the official continuation. Its README says it does not publish ready-made packages to CocoaPods, pub.dev or npm; you build it yourself with its Nix-based scripts.
nix --versionFix
Build the Apple frameworks with FFmpegKitNext's scripts on a Mac, then reference the result as a local pod (next cause).
git clone https://github.com/arthenica/ffmpeg-kit-next.git
# follow the Nix build instructions in its wiki for Apple platformsVerify
The build produces .xcframework bundles for iOS that you can vendor.
find . -name '*.xcframework' -maxdepth 4Confirmed by raw.githubusercontent.com
Cause 3 of 3
You already have a working copy of the frameworks
You seeAn older checkout, CI cache or Pods folder still contains the ffmpegkit .xcframework bundles
Check
CocoaPods can install a pod from a local folder with :path, and a podspec can ship prebuilt .xcframework bundles through vendored_frameworks. That removes the download entirely.
find ~/Library/Caches/CocoaPods ios/Pods -name 'ffmpegkit.xcframework' 2>/dev/null | headFix
Store the frameworks in the repo (or a private artifact store you control), write a small local podspec, and point the Podfile at it. Keep the GPL or LGPL licence terms of the build you vendor.
# vendor/ffmpegkit/ffmpegkit-local.podspec
Pod::Spec.new do |s|
s.name = 'ffmpegkit-local'
s.version = '6.0'
s.summary = 'Vendored FFmpegKit frameworks'
s.homepage = 'https://github.com/arthenica/ffmpeg-kit'
s.license = { :type => 'LGPL-3.0' }
s.author = 'vendored'
s.source = { :path => '.' }
s.platform = :ios, '12.1'
s.vendored_frameworks = '*.xcframework'
end
# ios/Podfile
pod 'ffmpegkit-local', :path => '../vendor/ffmpegkit'Verify
pod install uses the local pod and no network download of ffmpeg-kit is attempted.
cd ios && pod install --verbose | grep -i ffmpegConfirmed by guides.cocoapods.org
How do I stop it coming back?
- Check the README of native-binary dependencies for archive or retirement notices before each release.
- Cache or vendor prebuilt native frameworks your app cannot ship without.
- Keep Podfile.lock in version control so you can see which pod pulled in a dependency.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.