• Replies 5 replies
  • Subscribers 20 subscribers
  • Views 2383 views
  • Users 0 members are here
Options
Related

BLE Queue Full

lustyd

Is anyone else seeing issues with Bluetooth on IOS at the moment? An app that has worked fine in the past has suddenly started hitting BLE Queue full errors after a few minutes of operation. The app (eventhubapp) just hits an API endpoint with info on a timer which was always set to 1 second in the past and worked. I tried changing to 2 seconds and still getting the issue so it's like IOS is timing out the Bluetooth connection for some reason.

I can't think of anything else I can test that's under my control so feeling like it's a bug somewhere. Any ideas on how to proceed would be most welcome. Is there a way to get support through Garmin for this type of thing? I can't imagine their usual support number would be too impressed with me calling up and moaning about my own app not working!

AAARGH! and now even the forum is telling me I'm posting too frequently despite this being my first post of the day :o/

  • There is a max of 3 outstanding requests - requests sent with no response yet.

    Sending every second could be a problem itself, as due to network delays, etc, as that could be VERY tight.  What you might want to consider is when you send a request, wait for the response before you send the next one.

  • in reply to jim_m_58

    Thanks for the reply Jim. It's never been an issue in the past, hence my questioning if it's a bug with the new IOS. The error is with Bluetooth rather than with the API call so I don't think that would help anyway. I can test making the delay even longer I guess, but at 2 seconds there should be more than enough time. Also, if I stop the app and restart the issue is usually still present so unlikely to be an app queue issue?.

  • in reply to lustyd

    There does seem to be a problem with GCM/iOS, but with the queuing I suggested, it may help a bit (a work-around).  Having 3 outstanding requests was an issue with GCM/A in the past, so queuing could help there too.

  • in reply to jim_m_58

    Thanks Jim, I've done a bit more testing and it seems once the queue is full no requests are getting through to the server. If it were a queue I'd expect that queue to still process at a slower rate so I'm still definitely thinking bug. Might even have to get an Android phone for testing purposes!

  • OK I bought a new Android phone, and after battling with GCM to pair my Fenix 5 (and nearly throwing both at the wall in frustration, thanks Garmin!) I did some testing.
    I can saturate the BLE queue on the Android too, but it will recover almost immediately and in any case continues to send requests out to the Internet. On the iPhone this breaks connectivity on the watch to the phone/Internet and doesn't recover or send requests. That definitely seems like a bug in GCM iOS to me. Happens on various devices and only on iOS so unlikely a bug at the watch end. Is there a process to submit bugs to Garmin outside of the support line?