Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Expose all GAP Characteristics to CoreBluetooth clients

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Expose all GAP Characteristics to CoreBluetooth clients

Subject: Re: Expose all GAP Characteristics to CoreBluetooth clients
From: François Beaufort 🇫🇷 <email@hidden>
Date: Mon, 20 Jun 2016 15:03:26 +0200

Thank you really much Stuart!

I didn't realize this mailing list wasn't a good place for feature requests.

I'll file a FR at bugreport.apple.com then.

On Tue, Jun 14, 2016 at 9:59 PM, Stuart Smith <email@hidden> wrote:

The mailing lists aren't a good place for feature requests. The lists are
mostly for developers to help other developers, sometimes Apple employees
answer questions (on their own time), but it isn't Developer Tech Support,
nor is it an official feedback route.

Apple maintains a database of bugs and feature request, accessible via
bugreport.apple.com. You can enter feature requests there. They'll want to
know _why_ you want/need the feature, and _why_ the workaround is
unacceptable.

You only have one question in your post - "Could we simply
un-blacklist...". I'm pretty sure the answer has to be "no", it isn't
something we (the bluetooth-dev readership) have any control over.

Stuart

On 6/14/16, 12:00 PM,
"bluetooth-dev-bounces+stuart=email@hidden on behalf of
email@hidden"
<bluetooth-dev-bounces+stuart=email@hidden on behalf of
email@hidden> wrote:

>Message: 1
>Date: Tue, 14 Jun 2016 08:28:53 +0000
>From: François Beaufort 🇫🇷 <email@hidden>
>To: email@hidden
>Subject: Expose all GAP Characteristics to CoreBluetooth clients
>Message-ID:
> <email@hidden">email@hidden>
>Content-Type: text/plain; charset="utf-8"
>
>According to a previous thread (
>http://lists.apple.com/archives/bluetooth-dev/2016/Feb/msg00018.html),
>iOS
>does not expose the GAP service directly to CoreBluetooth clients.
>
>This means I can't read some GAP characteristics such as *Appearance*,
>*Peripheral
>Preferred Connection Parameters*, *Central Address Resolution* and
>*Peripheral
>Privacy Flag* which are accessible on Android Bluetooth APIs for instance.
>
>The workaround of creating a custom service which would hold same
>characteristics is not that exciting. Could we simply un-blacklist the GAP
>Service and its Characteristics so that CoreBluetooth clients which need
>this info can have it?
>
>Thanks in advance,
>Francois.

 _______________________________________________
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

Follow-Ups:
- Re: Expose all GAP Characteristics to CoreBluetooth clients
  - From: Stuart Smith <email@hidden>

References:
	>Expose all GAP Characteristics to CoreBluetooth clients (From: Stuart Smith <email@hidden>)

Prev by Date: Re: Do Not Disturb functionality over Bluetooth
Next by Date: Re: Expose all GAP Characteristics to CoreBluetooth clients
Previous by thread: Expose all GAP Characteristics to CoreBluetooth clients
Next by thread: Re: Expose all GAP Characteristics to CoreBluetooth clients
Index(es):
- Date
- Thread