GitHub Issue #126Community Verified Solution
Fix AirCard "No iPhone (USB)" Error: Complete Diagnostic Guide
The "No iPhone (USB)" error occurs when AirCard cannot open an active communication socket with your iPhone over usbmuxd. The most common cause is using a charging-only cable, a passive USB hub lacking data throughput, or failing to grant USB accessory permissions on macOS.
GitHub Issue #26Resolved with Trust Reset & Permissions
AirCard Not Detecting iPhone: Step-by-Step Fixes
When AirCard does not detect your iPhone, it is usually because the macOS-to-iOS lockdown pairing certificate has expired or become corrupted, or the iPhone screen was locked during application initialization. Resetting device trust and re-authenticating resolves the issue.
GitHub Issue #131Investigated & Workaround Verified
Fix AirCard AirTraffic Sync Timeout: Step-by-Step Guide
AirTraffic sync timeouts occur when the iOS background sync daemon (AirTrafficHost / atc) takes longer than 30 seconds to acknowledge a pass artwork update. This is typically triggered by oversized artwork files, low iPhone storage space, or an active iCloud / iTunes backup in progress.
GitHub Issue #70Identified: Image Parsing / File Lock
Fix AirCard Card Flashing Stuck at 25% or Freezing
Flashing progress halts at 25% when AirCard finishes writing the image payload to temporary storage but the iOS PassKit validation subsystem rejects the image format or encounters a file permission lock on the target .pkpass bundle.
GitHub Issue #112Verified Solution: Lockdown Reset
How to Resolve iPhone Pairing & Trust Errors in AirCard
Pairing errors occur when the cryptographic certificate stored between macOS and iOS in the lockdown directory becomes mismatched or revoked. Deleting the stale pairing record and reconnecting restores the security relationship.
GitHub Issue #118Documented Architecture Limitation
Why AirCard Artwork Does Not Sync to Apple Watch: Causes & Solutions
AirCard updates card artwork directly within the iPhone local filesystem. However, Apple Watch maintains an isolated, independent pass image cache managed by the Companion WatchKit sync service. Consequently, customized card artwork does not immediately replicate to watchOS without specific cache invalidation.
GitHub Issue #114Investigated & Documented Workaround
Fix AirCard Stuck in "ReadyForSync" State: Step-by-Step Guide
"ReadyForSync" indicates that AirCard has established a USB socket with the iPhone but is awaiting an acknowledgment token from the iOS device management agent. If the iPhone screen locks or another system process holds an exclusive lock on the pass database, the handshake hangs.
Our Troubleshooting Methodology
Troubleshooting iOS-to-Mac USB communication requires a structured diagnostic method. We adhere to the following principles:
- Prioritize Reversible Actions: We always begin with non-destructive checks (cable verification, screen unlock, simple reboot) before suggesting resets of network or pairing certificates.
- Separate Fact from Speculation: If an issue remains unresolved upstream, we clearly document it as an open question rather than inventing unconfirmed fixes.
- Direct Link to Source Issues: Every article includes the exact upstream GitHub Issue URL so users can verify the discussion firsthand.
