[CoreBluetooth] API MISUSE: can only accept this command while in the powered on state（iOS蓝牙）

2020-06-01 17:28:14 900 收藏
分类专栏： ios
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/baidu_40537062/article/details/106477935
版权
已标记关键词 清除标记
iOS CoreBluetooth 教程
jimoduwu的专栏
05-12 3万+
Core Bluetooth for iOS 6 CoreBluetooth的API是基于BLE4.0的标准的。这个框架涵盖了BLE标准的所有细节。仅仅只有新的iOS设备和Mac是和BLE标准兼容的：iPhone4S，iPhone5，MacMini，New iPad,MacBook Air,MacBook Pro。还有iPhone iOS6的模拟器也支持。这是非常有用的，在你没有一个真正的iOS
表情包
插入表情
还能输入1000个字符
相关推荐
ios蓝牙开发（四）BabyBluetooth蓝牙库介绍
洛阳如是
09-25 1315
BabyBluetooth 是一个最简单易用的蓝牙库，基于CoreBluetooth的封装，并兼容ios和mac osx。 特色： 基于原生CoreBluetooth框架封装的轻量级的开源库，可以帮你更简单地使用CoreBluetooth API。CoreBluetooth所有方法都是通过委托完成，代码冗余且顺序凌乱。BabyBluetooth使用block方法，可以重新按照功能和
iOS BLE 开发小记[4] 如何实现 CoreBluetooth 后台运行模式
weixin_33854644的博客
04-22 220
欢迎访问我的博客 muhlenXi，该文章出自我的博客，欢迎转载，转载请注明来源: muhlenxi.com/2017/05/03/…。 导语： 在这一节，主要是 iOS APP 关于蓝牙后台处理方面的知识和经验。 对于 iOS APP 来说，知道你的 APP 是运行在前台还是运行在后台很重要。一个 APP 在后台运行状态下的行为表现必须不同于前台，因为 iOS 设备的系统资源是有限的。关于 ...
iOS开发中APP在后台运行与扫描蓝牙遇到的坑
JR的博客
04-18 3544
后台长久任务： 打开后台模式中的使用蓝牙功能(手机为中心模式)：TARGET→Capabilities→Background Modes→Uses Bluetooth LE accessories(勾选) 在AppDelegate.m中添加下面代码： #pragma mark APP进入后台触发的方法 - (void)applicationDidEnterBackground:(UIApp...
卡巴升级包制做 - blog.lei - powered by phpwind.net
happy5856的专栏
11-06 1441
导读： 　　echo off 　　if exist kav6 goto begin 　　md kav6 　　:begin 　　C: 　　cd/Documents and Settings/All Users/Application Data/Kaspersky Lab/AVP6 　　copy Bases/*.* d:/kav6 　　copy Data/*.* d:/kav6 　　copy
Connect to other devices
12-25
<div><p><strong>Information</strong> This GitHub Issue page is for reporting issues or asking questions regarding the iOS DFU library. For general DFU questions, SDK questions, etc, please check our <a href="https://devzone.nordicsemi.com/">DevZone</a>. Make sure you are using the latest version of the library: <a href="http://cocoapods.org/pods/iOSDFULibrary"><img alt="Version" src="http://img.shields.io/cocoapods/v/iOSDFULibrary.svg" /></a> Also, before creating a new issue, make sure similar issue isn't already opened in <a href="https://github.com/NordicSemiconductor/IOS-Pods-DFU-Library/issues">open</a> or <a href="https://github.com/NordicSemiconductor/IOS-Pods-DFU-Library/issues?q=is%3Aissue+is%3Aclosed">closed</a> issues.</p> <p><strong>Device information (please complete the following information):</strong> - Device: iPhone 8 - OS: 13.3</p> <p><strong>Describe the bug</strong> Hello, I have a device called FATTO.</p> <p>When I launch the DFU it works 1 time out of 10.</p> <p>All the other times when it does not work, it is because after changing the name of the device it connects to another device (to an iMac / other device ble / unknown device, ...), or I get error 302</p> <p>In the room there are some ble devices.</p> <p>Why after having changed the name of the Fatto device, it disconnects and connects to another device ??</p> <p><strong>First Log</strong></p> <pre><code> Connecting  [Callback] Central Manager did update state to: Powered ON  Connecting to FATTO...  centralManager.connect(peripheral, options: nil)  [Callback] Central Manager did connect peripheral  Connected to FATTO  Discovering services...  peripheral.discoverServices(nil)  Services discovered  Starting Secure DFU...  Connected to FATTO  Services discovered  Secure DFU Service found  Discovering characteristics in DFU Service...  peripheral.discoverCharacteristics(nil, for: FE59)  DFU characteristics discovered Starting  Enabling indications for 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.setNotifyValue(true, for: 8EC90003-F315-4F60-9FB8-838830DAEA50)  Indications enabled for 8EC90003-F315-4F60-9FB8-838830DAEA50  Buttonless DFU indications enabled  Application with buttonless update found Enabling DFU Mode  Trying setting bootloader name to Dfu92741  Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.writeValue(0x02084466753932373431, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)  Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50  Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200201  Response (Op Code = 2, Status = 1) received  Bootloader name changed successfully  Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.writeValue(0x01, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)  Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50  Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200101  Response (Op Code = 1, Status = 1) received imediate  [Callback] Central Manager did disconnect peripheral  Disconnected by the remote device  Scanning for the DFU Bootloader... 2020-02-03 12:31:12.207149+0200 fatto[1643:729929] [CoreBluetooth] API MISUSE: <cbperipheral: identifier="396215C7-F83E-8584-BAA3-E669AF7B95F1," name="FATTO," state="disconnected"> can only accept commands while in the connected state  DFU Bootloader found  Connecting to Unknown device.. // Why does it connect to another device?  centralManager.connect(peripheral, options: nil) </cbperipheral:></code></pre> <p><strong>Second Log</strong></p> <pre><code> Connecting  [Callback] Central Manager did update state to: Powered ON  Connecting to FATTO...  centralManager.connect(peripheral, options: nil)  [Callback] Central Manager did connect peripheral  Connected to FATTO  Discovering services...  peripheral.discoverServices(nil)  Services discovered  Starting Secure DFU...  Connected to FATTO  Services discovered  Secure DFU Service found  Discovering characteristics in DFU Service...  peripheral.discoverCharacteristics(nil, for: FE59)  DFU characteristics discovered Starting  Enabling indications for 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.setNotifyValue(true, for: 8EC90003-F315-4F60-9FB8-838830DAEA50)  Indications enabled for 8EC90003-F315-4F60-9FB8-838830DAEA50  Buttonless DFU indications enabled  Application with buttonless update found Enabling DFU Mode  Trying setting bootloader name to MyFattoDFU // Custom name  Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.writeValue(0x02084d7920466974746f, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)  Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50  Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200201  Response (Op Code = 2, Status = 1) received  Bootloader name changed successfully  Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.writeValue(0x01, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)  Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50  Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200101  Response (Op Code = 1, Status = 1) received  [Callback] Central Manager did disconnect peripheral  Disconnected by the remote device  Scanning for the DFU Bootloader...  DFU Bootloader found with name [TV] Samsung 7 Series (43) // Why does it connect to another device?  Connecting to [TV] Samsung 7 Series (43)...  centralManager.connect(peripheral, options: nil) </code></pre> <p><strong>Third log</strong></p> <pre><code> Connecting  [Callback] Central Manager did update state to: Powered ON  Connecting to FATTO...  centralManager.connect(peripheral, options: nil)  [Callback] Central Manager did connect peripheral  Connected to FATTO  Discovering services...  peripheral.discoverServices(nil)  Services discovered  Starting Secure DFU...  Connected to FATTO  Services discovered  Secure DFU Service found  Discovering characteristics in DFU Service...  peripheral.discoverCharacteristics(nil, for: FE59)  DFU characteristics discovered Starting  Enabling indications for 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.setNotifyValue(true, for: 8EC90003-F315-4F60-9FB8-838830DAEA50)  Indications enabled for 8EC90003-F315-4F60-9FB8-838830DAEA50  Buttonless DFU indications enabled  Application with buttonless update found Enabling DFU Mode  Trying setting bootloader name to Dfu05637  Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.writeValue(0x02084466753035363337, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)  Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50  Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200201  Response (Op Code = 2, Status = 1) received  Bootloader name changed successfully  Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...  peripheral.writeValue(0x01, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)  Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50  Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200101  Response (Op Code = 1, Status = 1) received  [Callback] Central Manager did disconnect peripheral  Disconnected by the remote device  Scanning for the DFU Bootloader...  DFU Bootloader found  Connecting to Michael 15" MacBook Pro... // Why??  centralManager.connect(peripheral, options: nil) 2020-02-03 12:12:43.365278+0200 fatto[1629:725403] [CoreBluetooth] API MISUSE: <cbperipheral: identifier="396215C7-F83E-8584-BAA3-E669AF7B95F1," name="FATTO," state="disconnected"> can only accept commands while in the connected state  [Callback] Central Manager did connect peripheral  Connected to Michael 15" MacBook Pro // ??  Discovering services...  peripheral.discoverServices([FE59])  Services discovered  DFU Service not found  No services found  Did you connect to the correct target? It might be that the previous services were cached: toggle Bluetooth from iOS settings to clear cache. Also, ensure the device contains the Service Changed characteristic  Disconnecting...  centralManager.cancelPeripheralConnection(peripheral)  [Callback] Central Manager did disconnect peripheral  Disconnected Error: 302 </cbperipheral:></code></pre> <p>My initiator is very simple:</p> <pre><code> let initiator = DFUServiceInitiator(queue: nil).with(firmware: firmware) initiator.delegate = self initiator.progressDelegate = self initiator.peripheralSelector = self initiator.logger = self </code></pre> <p>What is the problem?</p><p>该提问来源于开源项目：NordicSemiconductor/IOS-Pods-DFU-Library</p></div>
小弟开发android，遇到关于基于蓝牙的"电话本访问协议（PBAP）"的一个问题。。
02-03
小弟在Android系统上开发一个通过蓝牙获取他机联系人及通话记录的程序，参考相关资料后采用了PBAP协议，首先通过UUID：0000112f-0000-1000-8000-00805f9b34fb
linux 下忘记root密码的办法！
henrybai的专栏--大亨利白--大码
07-24 900
用GRUB引导系统进入单用户步骤：  (1) 启动GRUB，选择Red Hat Linux的选项，然后键入 e 来编辑；  (2) 选择以kernel开头的一行，再按e 键，在此行的末尾，按空格键后输入single，以回车键来退出编辑模式；  (3) 回到了 GRUB 屏幕后，键入 b 来引导进入单用户模式。 进入单用户后，更改password root 就可以了。
iOS Core Bluetooth 教程：心率监测
kmyhy的专栏
04-11 3274
原文：Core Bluetooth Tutorial for iOS: Heart Rate Monitor 作者：Jawwad Ahmad 译者：kmyhy 更新说明：本教程基于 Xcode 9 和 iOS 11，作者 Jawwad Ahmad。原版 O-C 教程作者是 Steven Daniel。 如今便携设备越来越盛行，设备之间的通信使得这些工具及其产生的数...
iOS10权限配置问题及上传Itunes审核注意事项
xiaohan.zhang的博客
02-24 302
iOS10新增了很多关于权限验证的配置，如果不配置而直接访问，会导致Crash。 NSBluetoothPeripheralUsageDescription 访问蓝牙 NSCalendarsUsageDescription 访问日历 NSCameraUsageDescription 相机 NS
坑：蓝牙集成的问题
lilang7的博客
07-21 414
蓝牙集成的时候有时候搜索没有反应很奇怪，后来查看控制台发现提示 # can only accept this command while in the powered on state 原来是需要先将蓝牙打开才能用。 所以搜索前，要先确定蓝牙的状态再进行搜索。...
基于蓝牙4.0（btle）的简单通讯流程
骑驴找马追骆驼_so的博客
06-19 5914
初始化一个CentralManager 在iOS10以后，需要在 Info.plist 文件里面设置 NSBluetoothPeripheralUsageDescription 字段，添加访问蓝牙权限的描述，否则上传程序是会被拒。CBCentralManager 的创建是异步的，如果初始化完成之后没有被当前创建它的类所持有，说白了如果是局部变量就会在控制台报错 bt
API MISUSE: ＜CBPeripheralManager: 0x282c00070＞ can only accept this command while in the powered on
baidu_40537062的博客
12-08 171
API MISUSE: <CBPeripheralManager: 0x282c00070> can only accept this command while in the powered on state XPC connection invalid //这里如果不用self.manager而是用let manager的话，会不弹出蓝牙授权框 //得在这个方法调用，peripheral: CBPeripheralManager状态为poweredOn的时候再添加service。 得用这个
https://github.com/coolnameismy/BabyBluetooth github上的一个ios 蓝牙4.0的库并带文档和教程...
weixin_33997389的博客
11-23 86
  The easiest way to use Bluetooth (BLE )in ios,even bady can use. 简单易用的蓝牙库，基于CoreBluetooth的封装，并兼容ios和mac osx. 为什么使用它？ 1：基于原生CoreBluetooth框架封装的轻量级的开源库，可以帮你更简单地使用CoreBluetooth API。 2：CoreBlueto...
蓝牙 CoreBluetooth
dod83985的博客
03-14 30
baseK(相关基础知识)蓝牙常见名称和缩写BLE:(Bluetooth low energy)蓝牙4.0设备因为低耗电,也叫BLEperipheral,central:外设和中心设备,发起链接的是central(一般是指手机),被链接的设备是peripheral(运动手环)service and characteristic:(服务和特征)每个设备会提供服务和特征,类似于服务端的API...
iOS 开发遇到的问题
weixin_34038293的博客
05-14 50
2019独角兽企业重金招聘Python工程师标准>>> ...
iOS 蓝牙 使用总结
Lydia的博客
01-31 1826
**后台唤醒的前提是：需要定位“始终允许”权限； background modes 中开启Uses Bluetooth LE accessories** self.cbManager = [[CBCentralManager alloc] initWithDelegate:self queue:nil]; 一调用，就会走代理- (void)centralManagerDidUpdateSta
v310增强型项目蓝牙集成的问题
海阔天空的专栏
10-22 550
已解决的问题： 1.扫描后再次扫描时，之前扫描到的设备不显示出来，后期处理后，设备显示出来了，但是已配对设备显示为未配对； 2.实现了获取远端设备是否配对和是否连接的功能； 3.实现了连接与取消连接远端设备的功能，并解决了取消连接响应有延迟的问题。 4.配对BLE遥控器已经能够成功，但是连接会失败； 目前存在的问题： 1. 配对后重启再次扫描，远
©️2020 CSDN 皮肤主题: 大白 设计师:CSDN官方博客 返回首页