[react native] app build fails after pod install ffmpegkit.xcframework/Info.plist doesn't exist

[Lakston]

Description We are experiencing build failures in our CI since this morning, nothing has changed in our repo, yesterday all pipelines were successfull we used v5.1.0 but also tried to update to latest

Build error after installing pods:

Generating Pods project
[!] The plist file at path `/[...long path...]/ios/Pods/ffmpeg-kit-ios-min-gpl/ffmpegkit.xcframework/Info.plist` doesn't exist.

Expected behavior build should succeed

Current behavior our pipeline fails at the Generating Pods project phase

Environment

• Platform: ReactNative
• Architecture: arm64
• Version: v6.0.2 / v5.1.0
• Source branch: main
• Xcode version: 14.2
• Cocoapods version: 1.10.3
• react-native info:

System:
OS: macOS 14.1.2
  CPU: (8) arm64 Apple M1 Pro
  Memory: 72.48 MB / 32.00 GB
Managers:
  CocoaPods:
    version: 1.14.3
    path: /Users/laks/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
IDEs:
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Ruby:
    version: 2.7.5
    path: /Users/laks/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.9
    wanted: 0.72.9
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: false
  newArchEnabled: false

Other Podfile

  pod 'ffmpeg-kit-react-native', :subspecs => ['min-gpl'], :podspec => '../node_modules/ffmpeg-kit-react-native/ffmpeg-kit-react-native.podspec'

[CleverMobile2811]

Same issue. It shows the Pod directory, not working.

[james-cohen]

Also happening on our XCode Cloud pipeline on v6.0.2, no changes but suddenly failing:

...
Installing ffmpeg-kit-ios-https (6.0)

Installing ffmpeg-kit-react-native (6.0.2)

Installing fmt (6.2.1)

Installing glog (0.3.5)

Installing hermes-engine (0.73.4)

Installing libevent (2.1.12)

Installing react-native-background-actions (3.0.1)

Installing react-native-blob-util (0.19.6)

Installing react-native-config (1.5.1)

Installing react-native-create-thumbnail (2.0.0)

Installing react-native-date-picker (4.3.5)

Installing react-native-get-random-values (1.10.0)

Installing react-native-netinfo (11.2.1)

Installing react-native-pager-view (6.2.3)

Installing react-native-safe-area-context (4.8.2)

Installing react-native-video (6.0.0-beta.4)

Installing react-native-worklets-core (0.2.4)

Generating Pods project

[!] The plist file at path `/Volumes/workspace/repository/pkg/app/ios/Pods/ffmpeg-kit-ios-https/ffmpegkit.xcframework/Info.plist` doesn't exist.

Error
Command exited with non-zero exit-code: 1

[james-cohen]

Seems like its now resolved, our pipeline is working again

[Lakston]

Same on our end, but I'd be interested to know what happened, feels free to close this issue if it was resolved for all 3 of us

[edicon]

Occurs on M1 Mac but not on Intel Mac

[tanersener]

iOS pods download binaries from GitHub, specifically from the assets uploaded to the releases page. It appears that a temporary error occurred on GitHub regarding the release bundles on that day.

[kdpadhiyar]

Its not working now `[!] Error installing ffmpeg-kit-ios-full-gpl [!] /usr/bin/curl -f -L -o /var/folders/xb/gl7ggpkx61ddr25b55zy_tsh0000gn/T/d20250417-11437-7z9hgi/file.zip https://github.com/arthenica/ffmpeg-kit/releases/download/v6.0.LTS/ffmpeg-kit-full-gpl-6.0.LTS-ios-framework.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.16.2 cocoapods-downloader/2.1'

% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 9 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (56) The requested URL returned error: 404 `

[tanersener]

@kdpadhiyar Read the project README!

[kdpadhiyar]

Its not helping you should address the concern batter way @tanersener

[tanersener]

@kdpadhiyar The repository will be archived soon so that anyone visiting it will immediately understand that the project has been retired. I initially kept it open to give users a space to discuss next steps. But apparently, that was a mistake. I’ve received a lot of criticism for it.

[kdpadhiyar]

@kdpadhiyar The repository will be archived soon so that anyone visiting it will immediately understand that the project has been retired. I initially kept it open to give users a space to discuss next steps. But apparently, that was a mistake. I’ve received a lot of criticism for it.

But I was not mean to criticise you bro, Apology if you feel that way.

I want to just continue the usage of it, I don't know how but its stopped working,So need help.

[tanersener]

@kdpadhiyar I’m not sure what you saw in the project README, so let me summarise it one more time. The README clearly states:

1. The project is retired. There won’t be any new releases from us going forward
2. The binaries from previous releases will be removed
3. The linked Medium article explains the reasons behind this decision.

Because of point 2, you can’t continue using the project the same way; since the binaries have been removed. If you still want to use it, you’ll need to build it yourself or use a maintained fork. This is all explained in the Medium article.