Re: Just bought a set of QC 35 II's ...
That's what I was told by a developer. I would love to get a definitive answer.
As I understand it, the argument goes like this :
If you want to search for and connect to your bluetooth device, you can search for arbitrary bluetooth devices.
If you can search for arbitrary bluetooth devices then you can see beacons.
Beacons provide location information.
Therefore if you want to search for bluetooth devices you must have been given permission to obtain location.
It may be that if you only use generic bluetooth services negotiated by the OS (such as bluetooth audio connections) or use a connection that has been paired through the OS's settings, there is no need for the location permission.
So it may be that the problem occurs because developers like to connect in-app rather than push users to the pairing setting. That's a reasonable requirement given the knowledge of the typical user, and google could support it in a useful way, which is why I blame google rather than the developers.
Actual explanation from a knowledgable developer welcome.