While AirBridge is designed to configure its network protocols automatically, strict corporate networks or specific hardware configurations can sometimes interfere with peer-to-peer transfers.
AES-256 Encryption
Security is paramount when bypassing standard cloud infrastructure. Every single byte transferred via AirBridge is encrypted end-to-end using AES-256-GCM.
The encryption keys are generated dynamically during the BLE handshake phase and are never transmitted over the Wi-Fi connection. This guarantees that even if someone is sniffing packets on a public coffee shop Wi-Fi network, they cannot intercept or decipher the files you are transferring.
Discovery Issues
If a device is not showing up in the AirBridge list:
- Bluetooth is off: Ensure Bluetooth is turned on for both devices. AirBridge requires BLE to advertise its presence.
- Proximity: The devices must be within roughly 10 meters of each other. Move them closer together.
- Permissions (macOS): Ensure you have granted AirBridge permission to access Bluetooth in
System Settings > Privacy & Security > Bluetooth. - Permissions (Android): Ensure AirBridge has been granted "Nearby Devices" and "Location" permissions, which are required by Android to use BLE scanning.
Network Isolation (AP Isolation)
If devices can discover each other via Bluetooth, but file transfers fail to start, the issue is likely your Wi-Fi router.
Many public Wi-Fi networks (hotels, airports) and some home "Guest" networks have a feature enabled called AP Isolation or Client Isolation. This security feature actively blocks devices on the same Wi-Fi network from communicating with each other.
Solution: Because AirBridge supports Wi-Fi Direct, you can often bypass this by temporarily disconnecting both devices from the public Wi-Fi network. AirBridge will fall back to creating its own direct hotspot, allowing the transfer to complete successfully even without a router.