I'm having this issue on Cave on 72.0.3609.3 (Official Build) dev (64-bit) and my OnePlus 6 lastest stock OS with beta Google Play Services. Previously I didn't even have the SmartLock option when you guys migrated over to Better Together but it reappeared. I tried disabling better together, restarting both devices, toggling the few Bluetooth related flags to see if any of those would fix it. So far I have not been able to actually unlock my device with SmartLock even though I can see my phone in the Bluetooth settings and I even paired it. Any suggestions on how to get this working again or do you think this is an actual bug?

I posted more information in this thread and if you need logs from either device anything feel free to contact me and I will pull them if I am able to.

https://www.reddit.com/r/chromeos/comments/a1qf8f/smart_lock_on_asus_flip_c302_cave_on_chrome_os_72/

There are some significant improvements to Smart Lock with M71, which should make it more robust moving forward.

That said, users on recent M71 builds are still reporting issues with Smart Lock.

Reports from 71.0.3578.71 beta:
- Pixel 2: https://listnr.corp.google.com/report/85818232981
- Pixel 3XL: https://listnr.corp.google.com/report/85816747135
- https://listnr.corp.google.com/report/85814776217

There's no single issue being discussed here, and 3 separate Chrome versions mentioned (67, 71, and 72). Moving to merge with existing issues...

- Original report, and linkofhyruleuo@gmail.com's issue, are being addressed at crbug.com/905523.
- https://listnr.corp.google.com/report/85818232981 logs are unfortunately not super helpful (no logs on the connection process), but they do show Smart Lock being successfully enabled, so I'm not concerned. My best guess from the user's message is that this is also crbug.com/905523 (flaky Bluetooth which is made more annoying by unclear UX language)
- https://listnr.corp.google.com/report/85816747135 looks like it is in the middle of waiting for host verification. The logs last for several minutes, and the features are only in state==kUnavailableNoVerifiedHost that whole time. Moving to new bug crbug.com/913816.
- https://listnr.corp.google.com/report/85814776217: Also clearly stuck in "waiting for verification" state. Let's move discussion for this to crbug.com/913816 as well.