If you’re using Packages (the popular macOS installer creation tool by Stéphane Sudre) and suddenly encounter the frustrating “packages_dispatcher is not responding” error during build, you’re not alone. This error prevents you from building installer packages and can halt your entire development workflow. The good news? There’s a quick command-line fix that resolves this issue instantly.
Understanding the packages_dispatcher Error
When you attempt to build an installer package in Packages and see the error message “packages_dispatcher is not responding. Have you disabled or unloaded the fr.whitebox.packages.build.dispatcher.plist launch configuration file?”, it indicates that the background dispatcher service responsible for coordinating build operations has become unresponsive or has been inadvertently unloaded.
The packages_dispatcher is a critical component that manages the communication between the Packages GUI application and the underlying build system. When this service fails to respond, the build process cannot proceed, resulting in the “Build Failed” status you see in the Build Log.
Common Causes of This Error
Based on community reports, common causes include macOS updates that disable or unload the LaunchDaemon, the dispatcher service crashing during intensive build operations, incorrect permissions on the plist configuration file, the service being unloaded manually via launchctl, and security software interfering with LaunchDaemon operations.
The One-Line Fix: One Terminal Command
Reloading the dispatcher LaunchDaemon is the most commonly reported way to clear this error.
Step 1: Open Terminal (Applications → Utilities → Terminal)
Step 2: Execute the following command:
sudo launchctl load -w /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist
What this command does:
sudo– Runs the command with administrative privileges (you’ll need to enter your password)launchctl load– Loads the specified LaunchDaemon service-w– Overwrites the disabled state, so the service starts and stays enabled- The plist path points to the dispatcher configuration file in the system LaunchDaemons directory
Expected Output: If successful, the command will complete without any error messages. Some users may see no output at all, which is normal for successful launchctl operations.
Checking That the Service Is Running
Method 1: Check Service Status
sudo launchctl list | grep packages.build.dispatcher
You should see output similar to:
- 0 fr.whitebox.packages.build.dispatcher
The presence of this line confirms the service is loaded and running.
To confirm the fix in Packages itself, reopen your project, choose Build → Build, and check that the Build Log finishes without errors and produces the installer package in your designated build directory.
Alternative Solutions and Troubleshooting
If the Primary Solution Doesn’t Work
Solution 1: Verify File Permissions
Check that the plist file has correct ownership and permissions:
ls -la /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist
The file should be owned by root:wheel with permissions similar to -rw-r--r--. If permissions are incorrect, fix them with:
sudo chown root:wheel /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist
sudo chmod 644 /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist
If the command instead returns “operation not permitted”, the issue is Full Disk Access rather than file ownership — grant Terminal access via System Settings → Privacy & Security → Full Disk Access, then run the command again.
Solution 2: Force Unload and Reload
If the service appears to be stuck, try forcefully unloading and reloading:
sudo launchctl unload /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist
sudo launchctl load -w /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist
Solution 3: Reinstall Packages
If all else fails, reinstalling Packages restores all necessary services: download the current release from Stéphane Sudre’s official website, quit Packages, drag the app to Trash and empty it, then install the fresh download — the installer automatically reconfigures all LaunchDaemons.
Prevention Tips
To reduce the chances of this happening again: avoid manually unloading Packages-related services unless you’re troubleshooting, keep Packages updated via the official website, re-check that its services are still loaded after major macOS updates, whitelist Packages and its LaunchDaemons in any security software, and periodically confirm service status with the launchctl list command.
Official Resources:
- Packages Official Website – Download and documentation
- Packages Documentation – User guide
- Apple Developer: Creating Launch Daemons – Understanding macOS services