Weird behavior on API >=23

Summary

When scanning for devices I’m getting devices with the wrong mac address on API >=23

Preconditions

Use a API >=23 device

Steps to reproduce actual result

 fun scanAppliances(): Observable<Appliance> {
        return rxBleClient.scanBleDevices()
                .flatMap flatMap@ { scanResult ->
                    val uuids = AdvertisedServiceUUIDExtractor().extractUUIDs(scanResult.scanRecord)
                    val uuid = uuids.firstOrNull { servicesUUIDs.contains(it) } ?: return@flatMap null //this just filters out unwanted uuids
                    val bleDevice = scanResult.bleDevice
                    Timber.tag("scanAppliances")
                    Timber.d("--------------------------------------------------------\nnew scanResult")
                    Timber.d("device name: ${bleDevice.name} with macAddrs: ${bleDevice.macAddress} rssi: ${scanResult.rssi} UUID: $uuid")
                    val appliance = Appliance( //this is just my internal POJO
                            bleDevice.name,
                            uuid.toString(),
                            null,
                            bleDevice.macAddress
                    )
                    Timber.d("appliance created")
                    return@flatMap Observable.just(appliance)
                }
    }

Actual result

When scanning for devices on API 22 I only get one reading of each device, just like on this log:

This is what I’m expecting.

Expected result

When scanning on API 23 and API 25 devices, I get a endless stream of readings of the same device. The bigger problem is that sometimes the device appears with the wrong mac address. Using nF Connect app I can see that the wrong address actually are from another devices that are near

[dariuszseweryn]

As far as I know on Android 5.0+ the old API is using the new scan under the hood anyway but give it a try. I expect to have the new API scan implemented in the library somewhere next week. At least in the Snapshot.

[dariuszseweryn]

Unfortunately it does not look like something that the library may fix if it works on another device properly. I cannot do more than suggest you to open an issue on Google’s issue tracker: https://issuetracker.google.com/issues?q=nexus 6p ble scan

Closing for now. If you will have more info or an idea what we could do from the library side - feel free to comment / reopen.

Best Regards