• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: No call to didDiscoverServices, requiring reboot of iOS device
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: No call to didDiscoverServices, requiring reboot of iOS device

  • Subject: Re: No call to didDiscoverServices, requiring reboot of iOS device
  • From: András Kövi <email@hidden>
  • Date: Tue, 12 Nov 2013 21:26:38 +0100
I suggest you open a TSI. You have described very thoroughly everything you tried so Apple engineers will return to you probably very soon and provide you a debugging profile or something. They have the means to collect relevant logs and will tell you the instructions for what to do next.

These kind of issues seem to have started to appear quite frequently so I guess the guys are either already working on the solution or are eager to find out what is going wrong. :)

Regards,
Andras


2013/11/12 Mike Robbins <email@hidden>
Hi all,

I have an nRF51822-based custom peripheral advertising one service.
In general, I am able to successfully use CoreBluetooth to selectively
scan, connect, retrieve services, retrieve characteristics, subscribe
to a notification, receive notify data, and handle automatic
re-connection -- working reliably, all without issues.

However, after using the device with multiple reconnects and multiple
restarts of my app, I am sometimes able to enter a strange state.  In
this state, I can successfully selectively scan and connect.  However,
the CBPeripheral's services field is nil (as usual), but my call to
discoverServices is never returned with a didDiscoverServices.  I am
able to successfully readRSSI during this time, and the device remains
connected until I terminate the connection.  After 10 seconds, my
watchdog timer kicks in and re-initiates the scan and connection, but
I can change the watchdog time and/or let this loop for hours, and the
didDiscoverServices will *never* call back.  The only "solution" is to
power-off and power-on my iOS device (tested on iOS 7.0.3 on iPhone
5S, iPad, and iPad mini).  Hard-killing my app has no effect.  Turning
Bluetooth off and on in Settings has no effect.  Power-cycling my
peripheral has no effect.  Having multiple or only a single powered-on
peripheral has no effect.  The only fix is to power-cycle the entire
iOS device.

Unfortunately, I do not have a reliable procedure to replicate this
state, but it happens for our developers a few times per day.

Has anyone experienced a similar issue and can suggest how to debug
further?  Many thanks in advance.

Mike
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >No call to didDiscoverServices, requiring reboot of iOS device (From: Mike Robbins <email@hidden>)

  • Prev by Date: No call to didDiscoverServices, requiring reboot of iOS device
  • Next by Date: RE: BLE central device as GATT server
  • Previous by thread: No call to didDiscoverServices, requiring reboot of iOS device
  • Next by thread: NSData issues transferring from Peripheral to Client
  • Index(es):
    • Date
    • Thread