In aioble the ScanResult.name gives <bound_method>. However, advertisement is fine

[brianreinhold]

This may be a bug in aioble.
I run a central app and make a device discoverable in 'setup' mode. It's advertisement contains the name 1BP100. I get ScanResult.name, print it and it is fine.
Now I reconnect after setting up and the advertisement name has changed to 0BP100a3490000. (Proprietary devices are a pain.). THis time when I print ScanResult.name I get (as shown below) <bound method>

LNI: Starting a new device search
mp_bluetooth_gap_scan_start
LNI: scanResult.device.bt addr:  b'\xc45@\xec\xe2\x1f'
LNI: scanResult.adv_data:  b'\x0f\t0BP10027080000\x02\x01\x06\x03\x03\tx'
LNI: scanResult:  Scan result: Device(ADDR_RANDOM, c4:35:40:ec:e2:1f) -83
LNI: scanResult.name:  <bound_method>
mp_bluetooth_gap_scan_stop
Task exception wasn't retrieved
future: <Task> coro= <generator object 'run_scanner' at 20013910>
Traceback (most recent call last):
  File "asyncio/core.py", line 1, in run_until_complete
  File "bt/async_central.py", line 139, in run_scanner
  File "bt/async_central.py", line 250, in _handle_welch_allyn_discovery
AttributeError: 'bound_method' object has no attribute 'startswith'

Note the name reports but the advertisement clearly shows the correct name. Of course when I try and get the first character in the name the above error is thrown, the systems crashes, VS Code has to be restarted and the PICO-W has to be power cycled.

What does scanResult.name is a even mean? Is aioble getting confused by the change in the advertisement data? It is ok in the spec for connectable advertisement data to change, though it often doesn't.

What task exception is not being retrieved? I am IN a task, I am not running one. (It could be in the library however).

---

I think I know what the problem was. I forgot scanResult.name is a method, not a field! I think that is the cause of the <bound method> error. All the other scanResult properties I was using were fields...and I even knew that at one time. That led me down a rabbit hole of trying to decode the advertisement name myself which I could do but could not get it to compare with the device name obtained elsewhere. Turned out my approach generated a unicode string and the library was giving me utf-8 strings. They had the same class, length, type, and printed identical but an == gave false. I was at a loss!