What is the practical limit for endpoint info size in bytes?

[jacoblubecki]

For example, see: ConnectionsClient#startAdvertising

The method accepts endpoint info as a byte array that I would like to use to share some basic info about the client which is advertising. Similar endpointInfo byte array arguments are used in a few other API signatures as well.

From some basic digging I have found:

• BLE has an advertising limit of 31 bytes
• Bluetooth 5.0 has an advertising limit of 255 bytes
• Network Service Discovery generically advertises up to "a few hundred bytes" (I think this varies depending on the NSD protocol specifics)

That being said, it appears that nearby connections includes some basic metadata of its own, which I assume contributes to these limits... And the API doesn't seem to guarantee a specific technology for each connection strategy, so it's hard to know which limitations might apply.

Is there a recommended practical limit to these for nearby connections?

I imagine nearby connections might have some underlying tricks to bypass this limitation, but the API documentation doesn't offer any guidance, so I figured I'd check.

[Xlythe]

131 bytes is the cap