使用32feet库蓝牙读取手机联系人遇Bad Request错误求助

Hey there, sorry to hear you're hitting that Bad Request error with 32feet while trying to pull contacts from a paired mobile device. Let's first cover quick fixes for the 32feet issue, then dive into alternative OBEX-based approaches to get those contacts.

先排查32feet的常见问题 #

Before jumping to alternatives, let's rule out simple fixes that might resolve the Bad Request error:

• Verify PBAP permissions: Most mobile devices require explicit permission to allow Phonebook Access Profile (PBAP) access. Double-check that your paired device has granted contact access to your app (sometimes this needs to be enabled in the Bluetooth pairing settings or device privacy menu).
• Check OBEX target path: PBAP typically uses paths like /telecom/pb or /pbap—if your code is targeting the wrong path (e.g., using the object push path instead), the device will reject the request.
• Validate OBEX headers: Ensure your request includes the correct Target header set to x-obex.phonebook-access. Mismatched headers are a common cause of Bad Request responses.

替代OBEX/PBAP实现方式 #

If fixing 32feet doesn't work, here are other reliable ways to fetch contacts via OBEX:

1. Use Windows Native Bluetooth API (UWP) #

For Windows development, the built-in Windows.Devices.Bluetooth API offers native PBAP support, avoiding third-party library dependencies. Here's a simplified example:

using Windows.Devices.Bluetooth;
using Windows.Devices.Bluetooth.Rfcomm;
using Windows.Devices.Enumeration;
using Windows.Storage.Streams;

// Locate paired Bluetooth devices
var pairedDevices = await DeviceInformation.FindAllAsync(
    BluetoothDevice.GetDeviceSelectorFromPairingState(true)
);

foreach (var deviceInfo in pairedDevices)
{
    var bluetoothDevice = await BluetoothDevice.FromIdAsync(deviceInfo.Id);
    if (bluetoothDevice == null) continue;

    // Connect to the PBAP service
    var rfcommServices = await bluetoothDevice.GetRfcommServicesForIdAsync(
        RfcommServiceId.PhonebookAccessPce
    );

    if (rfcommServices.Services.Count > 0)
    {
        var pbapService = rfcommServices.Services[0];
        var socket = new StreamSocket();
        await socket.ConnectAsync(
            pbapService.ConnectionHostName,
            pbapService.ConnectionServiceName
        );

        // Use the socket's InputStream/OutputStream to send OBEX GET requests
        // You can fetch contacts as vCard files directly from here
    }
}

This approach integrates tightly with Windows' Bluetooth stack, often offering better compatibility than third-party libraries.

2. BlueZ (Linux Platform) #

On Linux, BlueZ provides built-in PBAP tools and D-Bus APIs for contact retrieval:

• Command-line quick start: Use the pbap-client tool to pull contacts directly:

  pbap-client -b <device-mac-address> -p /telecom/pb pull all.vcf
  

• Programmatic access: Use the BlueZ D-Bus interface (e.g., with Python's dbus library) to send OBEX requests and parse vCard responses. This gives you full control over the PBAP interaction without relying on 32feet.

3. Manual OBEX/PBAP Implementation #

If you want full control over the protocol, you can manually build OBEX requests over RFCOMM (Bluetooth's serial-like protocol). Here's a C# snippet to get started:

using System.Net.Sockets;
using System.IO;

// Connect to the device's PBAP RFCOMM port (usually port 12)
var client = new TcpClient();
client.Connect("<device-mac-address>", 12);
var stream = client.GetStream();

// Build an OBEX GET request for the main phonebook
byte[] obexRequest = new byte[] {
    0x80, // OBEX GET command
    0x00, // Length (to be updated)
    0x01, // Header ID: Target
    0x13, // Target header length
    // Target value: x-obex.phonebook-access
    0x78,0x2D,0x6F,0x62,0x65,0x78,0x2E,0x70,0x68,0x6F,0x6E,0x65,0x62,0x6F,0x6F,0x6B,0x2D,0x61,0x63,0x63,0x65,0x73,0x73,
    0x03, // Header ID: Name
    0x0A, // Name header length
    // Phonebook path: /telecom/pb
    0x2F,0x74,0x65,0x6C,0x65,0x63,0x6F,0x6D,0x2F,0x70,0x62
};
// Update the request length field
obexRequest[1] = (byte)(obexRequest.Length - 2);
stream.Write(obexRequest, 0, obexRequest.Length);

// Read and parse the OBEX response (will contain vCard data)
byte[] responseBuffer = new byte[1024];
int bytesRead = stream.Read(responseBuffer, 0, responseBuffer.Length);
// Process the response to extract contact vCards

This requires familiarity with the OBEX and PBAP specs, but eliminates any library-related issues.

内容的提问来源于stack exchange，提问作者Gorka Astigarraga