ffmpeg-kit-macos-codesign-crash

FFmpeg Kit macOS Code Signing Crash

Problem

Flutter macOS app builds successfully but crashes immediately at launch with a library loading failure. The crash is caused by FFmpeg Kit's Full GPL variant having runtime dependencies on homebrew-installed libraries (like fontconfig) that fail macOS code signature validation.

Context / Trigger Conditions

• Platform: macOS only (iOS and Android are not affected)
• Package: Using ffmpeg_kit_flutter_new (Full GPL variant)
• Symptom: App builds successfully but crashes on launch
• Crash log shows:

  Library not loaded: /opt/homebrew/*/libfontconfig.1.dylib
  Referenced from: .../libswresample.framework/...
  Reason: code signature in (.../libfontconfig.1.dylib) not valid for use in process:
  mapping process and mapped file (non-platform) have different Team IDs
  

Root Cause

The ffmpeg_kit_flutter_new package is the "Full GPL" variant which includes many FFmpeg libraries for advanced features like text rendering (drawtext filter). These libraries have external dependencies on system fonts via libfontconfig.

On macOS, when the app tries to load libswresample.framework, it attempts to also load libfontconfig.1.dylib from homebrew. macOS code signing validation rejects this because the homebrew library has a different Team ID than your app.

Solution

Switch from ffmpeg_kit_flutter_new (Full GPL) to ffmpeg_kit_flutter_new_min (Minimal).

Step 1: Update pubspec.yaml

# Before
ffmpeg_kit_flutter_new: ^3.2.0

# After
ffmpeg_kit_flutter_new_min: ^3.1.0

Step 2: Update imports in all Dart files

// Before
import 'package:ffmpeg_kit_flutter_new/ffmpeg_kit.dart';
import 'package:ffmpeg_kit_flutter_new/ffprobe_kit.dart';
import 'package:ffmpeg_kit_flutter_new/return_code.dart';

// After
import 'package:ffmpeg_kit_flutter_new_min/ffmpeg_kit.dart';
import 'package:ffmpeg_kit_flutter_new_min/ffprobe_kit.dart';
import 'package:ffmpeg_kit_flutter_new_min/return_code.dart';