Skip to main content

Verify device connection

Before troubleshooting, ensure your device is properly connected:
  1. Device is unlocked
  2. USB cable is functional (try a different cable if available)
  3. Device shows a charging indicator when plugged in
  4. You’ve tapped “Trust This Computer” on the device

Platform-specific detection issues

Linux device detection

Linux relies on usbmuxd for device communication. Detection issues are often related to usbmuxd configuration or udev rules.
Verify that usbmuxd is active on your system:
systemctl status usbmuxd
If not running, start it:
sudo systemctl start usbmuxd
To enable it permanently:
sudo systemctl enable usbmuxd
Some distributions configure udev rules that stop usbmuxd when no devices are connected.Solution:
  1. Plug in your device first
  2. Then launch Impactor
  3. The device should be detected immediately
This is expected behavior on some distributions and not a bug.
Your user may not have permissions to access USB devices.Solution: Add your user to the plugdev group:
sudo usermod -aG plugdev $USER
Then log out and log back in for changes to take effect.
These distributions may require updated crypto policies:
sudo update-crypto-policies
After running this command, restart usbmuxd:
sudo systemctl restart usbmuxd
Then reconnect your device.
Some distributions may need custom udev rules for iOS devices.Create a file /etc/udev/rules.d/39-usbmuxd.rules with:
SUBSYSTEM=="usb", ATTR{idVendor}=="05ac", ATTR{idProduct}=="12[9a][0-9a-f]", MODE="0660", GROUP="plugdev"
Reload udev rules:
sudo udevadm control --reload-rules
sudo udevadm trigger

Windows device detection

iTunes from the Microsoft Store does not include the necessary drivers. You must install iTunes directly from Apple.
Impactor requires iTunes drivers to communicate with iOS devices on Windows.Solution:
  1. Download iTunes from Apple (not Microsoft Store)
  2. Install iTunes
  3. Restart your computer
  4. Connect your device
  5. Restart Impactor
The Apple Mobile Device USB Driver may not be running.Solution:
  1. Press Win+R and type services.msc
  2. Find “Apple Mobile Device Service”
  3. Right-click and select “Start” if it’s stopped
  4. Set Startup Type to “Automatic”
  5. Reconnect your device
Other iOS management software may interfere with device drivers.Solution:
  • Close other iOS management tools (3uTools, iMazing, etc.)
  • Restart the Apple Mobile Device Service
  • Try using a different USB port (USB 3.0 ports are recommended)

macOS device detection

macOS generally has the best device detection, but issues can still occur.Solution:
  1. Disconnect and reconnect the device
  2. Restart Impactor
  3. Check System Settings > Privacy & Security for any device access prompts
  4. Try a different USB port or cable
On Apple Silicon Macs, iOS app installation uses a special wrapper structure.If installation fails with bundle copy errors:
  1. Verify you have write permissions to /Applications/iOS
  2. Check available disk space
  3. Ensure Impactor has Full Disk Access in System Settings > Privacy & Security

Connection type issues

Impactor displays the connection type in brackets:
  • [USB] - Direct USB connection
  • [WiFi] - Network connection
  • [Unknown] - Connection type couldn’t be determined
On Linux, WiFi connectivity is limited due to usbmuxd constraints. Auto-refresh only works with USB connections.
For WiFi device connections:Requirements:
  • Device and computer on the same network
  • WiFi sync enabled in iTunes/Finder
  • Device previously paired via USB
Solution:
  1. Connect device via USB first
  2. Trust the computer on the device
  3. Enable WiFi sync in your device settings
  4. Keep both devices on the same network

Pairing and trust issues

You must trust the computer on your iOS device.Solution:
  1. Disconnect the device
  2. Reconnect the device
  3. Look for “Trust This Computer?” prompt on device
  4. Tap “Trust”
  5. Enter your device passcode
  6. Wait a few seconds, then check Impactor
iOS updates often invalidate the pairing file.Solution: Use the “Pair” utility in Impactor:
  1. Connect your device
  2. Go to Utilities page
  3. Click “Trust/Pair Device”
  4. Follow the prompts
Pairing files are stored by the system:
  • macOS: ~/Library/Lockdown/
  • Linux: /var/lib/lockdown/ or ~/.local/share/lockdown/
  • Windows: %ProgramData%\Apple\Lockdown\
If pairing files are corrupted:
  1. Delete the existing pairing files for your device
  2. Reconnect and re-trust the device
  3. Pair again using Impactor utilities

Multiple devices

Impactor can work with multiple devices simultaneously.To select a device:
  1. All connected devices appear in the device list
  2. Each device shows connection type [USB] or [WiFi] and device name
  3. Select the device you want to work with from the list
In rare cases, device IDs may conflict.Solution:
  1. Disconnect all devices
  2. Connect only the device you want to use
  3. Complete your task
  4. Reconnect other devices

Advanced troubleshooting

Check if usbmuxd detects your device:
usbmuxd -f -v
You should see log entries when plugging/unplugging the device.
Impactor uses the device UDID for identification.To find your device UDID:
  • macOS/Windows: Use iTunes or Finder
  • Linux: Use idevice_id -l
If the UDID shows as “00008XXX-XXXX…” your device is properly detected by the system.
Install libimobiledevice tools to test device connectivity:
# List devices
idevice_id -l

# Get device info
ideviceinfo

# Check device pairing
idevicepair pair
If these commands work, the issue is specific to Impactor. If they fail, it’s a system-level problem.

Still not working?

If your device still isn’t detected:
  1. Try a different USB cable (Apple-certified cables work best)
  2. Try a different USB port (avoid USB hubs)
  3. Restart your device
  4. Restart your computer
  5. Check for Impactor updates
  6. Review the error logs in Impactor (if available)
  7. Search GitHub Issues for your specific device model
When reporting device detection issues, include:
  • Your operating system and version
  • Device model and iOS version
  • Connection type (USB/WiFi)
  • Any error messages from Impactor
  • Output from idevice_id -l (Linux/macOS)

Build docs developers (and LLMs) love