Flutter macOS Duplicate Camera Plugin Fix
SkillMediaFix Flutter macOS build failure caused by duplicate camera plugins. Use when: (1) macOS build fails with "Ambiguous use of 'CameraMacosPlugin.register(with:)'" error, (2) Both camera_macos and camera_macos_plus are in pubspec.yaml, (3) Build worked before adding a new camera package. The plugins define the same class name causing Swift registration conflicts.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Flutter macOS Duplicate Camera Plugin Fix skill
What this skill tells your AI
The instructions your AI receives, as published by divinevideo/divine-mobile in .agents/skills/flutter-macos-duplicate-camera-plugin/SKILL.md and read by ahel’s review.
Problem
Flutter macOS builds fail when both camera_macos and camera_macos_plus packages are present
in pubspec.yaml. Both packages define the same CameraMacosPlugin class, causing Swift
registration ambiguity.
Context / Trigger Conditions
Error message:
Ambiguous use of 'CameraMacosPlugin.register(with:)'
Symptoms:
- macOS build fails during Swift compilation
- iOS build may still succeed (different plugin implementations)
- Error occurs in the generated plugin registration code
- May be accompanied by Xcode build system crashes or "stat cache file not found" errors
Common scenarios:
- Project has
camera_macosfor basic camera support - Added
camera_macos_plusfor additional features - Transitive dependency pulled in duplicate plugin
- Copied pubspec.yaml from another project with different camera requirements
Solution
-
Identify the duplicates - Check pubspec.yaml for both packages:
# Look for these: camera_macos: ^0.0.9 camera_macos_plus: ^0.0.3 -
Choose one to keep -
camera_macos_plusis generally preferred as it's a more feature-complete fork ofcamera_macos -
Remove the duplicate from pubspec.yaml:
# Keep only one: camera_macos_plus: ^0.0.3 # macOS camera support -
Clean thoroughly - The Xcode build system may be in a corrupted state:
flutter clean rm -rf build/ rm -rf macos/Pods/ rm -f macos/Podfile.lock rm -rf ~/Library/Developer/Xcode/DerivedData/Runner-* flutter pub get -
Rebuild:
flutter build macos
Verification
After the fix:
flutter build macoscompletes successfully- No "Ambiguous use" errors in build output
- The macOS app launches and camera functionality works
Example
Before (broken):
dependencies:
camera_macos_plus: ^0.0.3
divine_camera:
path: packages/divine_camera
camera_macos: ^0.0.9 # DUPLICATE - causes conflict
After (fixed):
dependencies:
camera_macos_plus: ^0.0.3 # macOS camera support (replaces camera_macos)
divine_camera:
path: packages/divine_camera
# camera_macos removed
Notes
camera_macos_plusis a community fork with additional features- If you specifically need
camera_macosinstead, removecamera_macos_plus - Check transitive dependencies with
flutter pub depsif duplicates reappear - The Xcode build system can get into corrupted states after this error; thorough cleaning (including DerivedData) may be required
- This is specific to macOS - iOS uses different camera plugin implementations
References
Signals
- GitHub stars
- 265
- Forks
- 55
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
flutter-macos-duplicate-camera-plugin- Source
- github.com/divinevideo/divine-mobile