Project Abandoned? Bluetooth scanning multiple user fast user switching issue.

[MacsInSpace]

Hi I have an issue but it looks like this is project is not taking pull requests from users or making fixes?
I'll probably more to the most recently active version from @Skyearn https://github.com/Skyearn/BLEUnlock
Either way I have a small issue.

With bluetooth scanning, if this is app installed and running under two user accounts BT scanning via the app fails to work on one of them.
It seems to be "first in first served"
Opening BLEUnlock as User1 works as expected. However, with Fast User Switching enabled, moving to User2 under Tahoe, I cannot scan for any devices.

Thanks for a great app!

[Skyearn]

I just tested the version 1.13.5 I release and created a new user. There is no problem with Bluetooth scanning.

[MacsInSpace]

Ok. That's odd. So both users scan with yours? (Via the app)
I get scan results for one user but not the other.
I'll retry this shortly and see if anything is logged.

[Skyearn]

Ok. That's odd. So both users scan with yours? (Via the app) I get scan results for one user but not the other. I'll retry this shortly and see if anything is logged.

Which version is used, v1.13.5 or v1.12?

[MacsInSpace]

Using v1.13.5 currently but it occurs with both versions.
What was interesting in my testing just now is that running via cl in Terminal scans as expected from both users.
However, when the application is started by clicking the Application, it does not scan via the 'second' user.
I ran via cl to see if I could get a log of the failure mode... but it worked as expected when launched that way.
Other ways the get a log?

[Skyearn]

Using v1.13.5 currently but it occurs with both versions. What was interesting in my testing just now is that running via cl in Terminal scans as expected from both users. However, when the application is started by clicking the Application, it does not scan via the 'second' user. I ran via cl to see if I could get a log of the failure mode... but it worked as expected when launched that way. Other ways the get a log?

I have successfully reproduced the issue, and the test results are quite discouraging. It appears to be a management conflict within the macOS bluetoothd process regarding multiple user sessions. Despite my attempts to release Bluetooth resources and put the app into a sleep state, the device remains unscannable in other user sessions. The only way to completely clear the resource lock is to terminate the process entirely before switching users.

Consequently, the only viable workaround for multi-user compatibility would be implementing a helper tool to kill the main process upon switching and relaunch it on login. However, this approach is overly intrusive and ungraceful—bordering on "malware-like" behavior. Therefore, I have decided to defer this issue until macOS bluetoothd introduces a more robust handling mechanism.

[MacsInSpace]

It's strange that both scan when running via command-line.
I'll add a launchd command to launch it to test instead of the built in "launch at login" item as well.
Ultimately, It's not a show stopper for me. Maybe just something to be aware of for users.
Thanks for your continued development.

[Skyearn]

It's strange that both scan when running via command-line. I'll add a launchd command to launch it to test instead of the built in "launch at login" item as well. Ultimately, It's not a show stopper for me. Maybe just something to be aware of for users. Thanks for your continued development.

This phenomenon is indeed interesting, but the reason behind it is also helpless. When starting through the command line, it is a sub-process of Terminal and is not restricted by the scheduling of CoreBluetooth.

[MacsInSpace]

For anyone else with this issue, here is a quick workaround:

Starting with launchd allows both users to scan.

Under ~/Library/LaunchAgents/

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Label</key>
	<string>local.BLEUnlock</string>
	<key>Program</key>
	<string>/Applications/BLEUnlock.app/Contents/MacOS/BLEUnlock</string>
	<key>RunAtLoad</key>
	<true/>
</dict>
</plist>```