Win11下BLE WriteClientCharacteristicConfigurationDescriptorAsync等异步函数失效问题

问题背景 #

原生C++ BLE管理DLL在Win10上稳定运行多年，升级至Win11 21H2（内部版本22000.856）后出现两类异步函数回调无响应问题：

• 带缓存模式的服务发现函数：GetCharacteristicsWithCacheModeAsync、GetDescriptorsWithCacheModeAsync无回调，替换为无缓存的GetCharacteristicsAsync/GetDescriptorsAsync后恢复正常。
• 描述符写入函数：WriteClientCharacteristicConfigurationDescriptorAsync及WriteClientCharacteristicConfigurationDescriptorWithResultAsync均无法触发回调，当前采用ComPtr+事件模拟await的实现逻辑，而微软官方co_await示例可正常运行。

描述符写入核心代码 #

//Try to write the correct "value" on the descripton  
ComPtr<IAsyncOperation<enum GattCommunicationStatus>> writeOp;
HRESULT hr = charac->getChar()->WriteClientCharacteristicConfigurationDescriptorAsync(value, &writeOp);

if (ifFailedPrintErrorMessage(hr, "Can't write descriptor async")) {
     return E_FAIL;  
}

//Create event to simulate "await"
Event asyncCompletedWriteDescri(CreateEventEx(nullptr, nullptr, CREATE_EVENT_MANUAL_RESET, WRITE_OWNER | EVENT_ALL_ACCESS));  
HRESULT resultAsyncActionWriteDescri = S_OK;  

//Callback    
hr = writeOp->put_Completed(Callback<IAsyncOperationCompletedHandler<GattCommunicationStatus>>([this, charac, &resultAsyncActionWriteDescri, &asyncCompletedWriteDescri](IAsyncOperation<GattCommunicationStatus> *op, AsyncStatus status) {

     //Get Result
     GattCommunicationStatus result;
     HRESULT hr = op->GetResults(&result);  
     if (ifFailedPrintErrorMessage(hr, "Can't get writeDescriptor result")) {
        resultAsyncActionWriteDescri = E_FAIL;
        SetEvent(asyncCompletedWriteDescri.Get());
        return E_FAIL;
     }

     //Check if it's a success
     if (result != GattCommunicationStatus_Success) {
         std::cout << "Can't open pipe" << endl;
         resultAsyncActionWriteDescri = E_FAIL;
         SetEvent(asyncCompletedWriteDescri.Get());
         return E_FAIL;
     }

     //Register characteristic to ValueChanged
     if (registrerCharToValueChanged(charac) == E_FAIL) {
         resultAsyncActionWriteDescri = E_FAIL;
         SetEvent(asyncCompletedWriteDescri.Get());
         return E_FAIL;
     }

     resultAsyncActionWriteDescri = S_OK;
     SetEvent(asyncCompletedWriteDescri.Get());
     return S_OK;
}).Get());

//If the put_Completed function failed
if (ifFailedPrintErrorMessage(hr, "Can't call put_Completed for write descriptor async")) {
     return E_FAIL;
}

//Wait until the callback IAsyncOperationCompletedHandler is raised
WaitForSingleObject(asyncCompletedWriteDescri.Get(), INFINITE);
return resultAsyncActionWriteDescri;

问题分析与解决建议 #

1. 缓存模式API失效问题 #

Win11对BLE本地缓存机制做了逻辑调整，可能存在缓存同步异常：

• 缓存模式下系统优先读取本地缓存，若缓存数据未正确更新或存在损坏，会导致异步操作无响应。
• 临时解决方案：继续使用无缓存版API；若需保留缓存模式，可尝试调用GattDeviceService::RefreshCacheAsync强制刷新缓存后再执行带缓存的异步操作，验证是否恢复正常。

2. 描述符写入回调失效问题 #

（1）线程上下文与消息循环问题

WinRT异步回调依赖调用线程的消息循环调度：

• 检查执行WriteClientCharacteristicConfigurationDescriptorAsync的线程是否为STA线程，且是否运行活跃的消息循环（如GetMessage/DispatchMessage循环）。若线程无消息循环，回调无法被触发。
• 若为后台无消息循环线程，可切换到UI线程或带消息循环的工作线程执行异步操作，或显式调用IAsyncOperation::Start启动操作。

（2）ComPtr与回调捕获变量的生命周期

• 确保writeOp在回调触发前未被销毁：当前代码中writeOp为局部变量，WaitForSingleObject会阻塞至事件触发，此问题概率较低，但需排查函数是否存在提前退出的分支。
• 检查回调中捕获的charac、resultAsyncActionWriteDescri、asyncCompletedWriteDescri是否在回调触发时仍有效，避免因变量提前销毁导致回调逻辑异常。

（3）改造为co_await兼容逻辑

无需放弃ComPtr即可改造为co_await风格，解决线程阻塞问题：

• 确保项目启用C++/WinRT支持，将函数改为异步类型，示例如下：

winrt::fire_and_forget WriteCCCDAsync(ComPtr<GattCharacteristic> charac, GattClientCharacteristicConfigurationDescriptorValue value)
{
    GattCommunicationStatus status = co_await charac->WriteClientCharacteristicConfigurationDescriptorAsync(value);
    if (status != GattCommunicationStatus_Success)
    {
        std::cout << "Can't open pipe" << std::endl;
        co_return;
    }
    if (registrerCharToValueChanged(charac) == E_FAIL)
    {
        co_return;
    }
}

• 若无法直接改为异步函数，可使用winrt::resume_on_signal替代WaitForSingleObject，避免阻塞线程导致回调无法调度。

（4）Win11权限调整

Win11对BLE设备访问权限管控更严格：

• 检查宿主进程是否在清单中声明<DeviceCapability Name="bluetooth"/>权限，即使是DLL，宿主进程也需正确配置权限。
• 尝试以管理员身份运行程序，验证是否因权限不足导致操作无响应。

总结 #

优先排查线程消息循环与权限配置，其次尝试改造为co_await异步逻辑；缓存模式API问题可先使用无缓存版，或尝试强制刷新缓存后测试，若仍无效可等待微软后续兼容性修复。

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