Bluetooth devices include ordinary BLE devices and BLE Beacon devices (called ibeacon devices internally in Tuya). If you want to perform Bluetooth search on Android12 and above mobile phones without applying for location permission, you must set usesPermissionFlags="neverForLocation" in the manifest file. Flag, this is packaged and configured into the APP installation package. It does not support dynamic insertion during APP running. After you set this flag, all ordinary BLE devices can be discovered by Bluetooth scanning without applying for location permission, but BLE Beacon device broadcasts will be filtered out by the system, that is, we cannot perform corresponding business functions by receiving BLE Beacon broadcasts, such as anti-lost, anti-wolf, and proximity unlocking functions. But if you remove the usesPermissionFlags="neverForLocation" flag, you will not be able to search for ordinary BLE devices.
In other words, this flag usesPermissionFlags="neverForLocation" is mutually exclusive for ordinary BLE devices and BLE Beacon devices, and it is necessary to determine whether to add this flag when the APP packages the installation package, that is, when no application for positioning permission is required. Under this logo, we can only choose between supporting ordinary BLE devices and BLE Beacon devices, so we chose to continue to apply for positioning permissions.
Why is the current Bluetooth distribution network of Tuya public version APP still applying for positioning permission i
Why is the current Bluetooth distribution network of Tuya public version APP still applying for positioning permission i
Re: Why is the current Bluetooth distribution network of Tuya public version APP still applying for positioning permissi
Is it possible to inform users about the reason for requesting location permission when applying for it in the app? Or can an additional explanation be provided to help users understand this practice better?
Immersed in the beauty of mountains and rivers.