-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blueutil binary not working on silicon Macs #35
Comments
Running this command within the workflow directory
returns this
|
I'll need some debugging info if you want me to take a look at it. Your command line return indicates that there is no quarantine on that file, so the issue is somewhere else. |
Yes, how can I provide the debugging info? Is there a log file somewhere? |
Take a screenshot from the outout of the Workflow Debugger |
Might be that I accidentally removed cross compatibility in the last update. Try to replace the blueutil binary file with the one below (or install the alternative workflow, also below; in that case, the commands for on/off are 'btw' and 'bty'), and see if that fixes it. Edit: I have to ask you to do it, because I don't have a computer with apple silicon myself. |
@vegardinho the above file still does not fix this issue on apple silicon. I am having this exact same issue. I used your alternative workflow (in the zip file). |
Can you try this workflow? Make sure to delete or rename the commands of the old workflow first. |
Hi @vegardinho, unfortunately that did not solve my problem. Still getting the following issue in the debugger. [19:19:55.075] Logging Started... |
Can you try running the binary below directly?
Does it run as expected? Also, if you could install blueutil with homebrew/macports/other and send me the installed version (check where it is by running |
After running the terminal commands, I get; For blueutil version; Looking forward to solving this issue. |
@JSFLJ Could you also do this?
Essentially, I'm trying to figure out whether the binary provided by homebrew/macports is universal or targeted against specific architecture (apple chip/intel). |
I will do this in a few weeks and let you know.
On Wed, Jan 03, 2024 at 7:06 AM, vegardinho ***@***.******@***.***>> wrote:
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@JSFLJ<https://github.com/JSFLJ> Could you also do this?
Also, if you could install blueutil with homebrew/macports/other and send me the installed version (check where it is by running whereis blueutil), that would be great.
Essentially, I'm trying to figure out whether the binary provided by homebrew/macports is universal<https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary> or targeted against specific architecture (apple chip/intel).
—
Reply to this email directly, view it on GitHub<#35 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVCBSEKZV5LUV5LDTQB4HBLYMVCV3AVCNFSM6AAAAAAUYL4QPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVGI3TCNJUGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
This beta version works well on Sonoma 14.5, M1 Chip. Thank you for making this workflow🥳 |
@rh10hd could you please tell me step-by-step how you did it please?
|
@JSFLJ Don't forget to allow Alfred to have access to bluetooth. That's the point, I found that it was this step that caused the workflow to not work. Once I opened the setting, the workflow worked immediately! BTW, when you try to Remove quarantine using terminal for I hope this would help you. |
That helped! THANK YOU! ITS WORKING NOW 😄
…________________________________
From: rh10hd ***@***.***>
Sent: Saturday, July 27, 2024 1:34 AM
To: vegardinho/alfred_bluetooth_controller ***@***.***>
Cc: Jawwad Siddiqui ***@***.***>; Mention ***@***.***>
Subject: Re: [vegardinho/alfred_bluetooth_controller] bton does not turn on bluetooth. (Issue #35)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@rh10hd<https://github.com/rh10hd> could you please tell me step-by-step how you did it please?
Can you try this workflow? Make sure to delete or rename the commands of the old workflow first. Bluetooth Controller Beta.zip<https://github.com/vegardinho/alfred_bluetooth_controller/files/12568013/Bluetooth.Controller.Beta.zip>
This beta version works well on Sonoma 14.5, M1 Chip. Thank you for making this workflow🥳
@JSFLJ<https://github.com/JSFLJ>
I deleted the older version, downloaded the beta version and followed the Installation<https://github.com/vegardinho/alfred_bluetooth_controller?tab=readme-ov-file#installation> step by step. You can check the dependencies in Alfred preferences<https://www.alfredapp.com/help/kb/dependencies/> first. I guess that might help a bit.
Don't forget to allow Alfred to have access to bluetooth<https://github.com/vegardinho/alfred_bluetooth_controller?tab=readme-ov-file#allow-alfred-to-control-bluetooth>. That's the point, I found that it was this step that caused the workflow to not work. Once I opened the setting, the workflow worked immediately!
BTW, when you try to Remove quarantine using terminal<https://github.com/vegardinho/alfred_bluetooth_controller?tab=readme-ov-file#remove-quarantine-using-terminal> for blueutil or notificator, it may return xattr: ./blueutil: No such xattr: com.apple.quarantine. Don't worry, I tried several times and the same thing happened. Just make sure you've installed both of them as required.
I hope this would help you.
—
Reply to this email directly, view it on GitHub<#35 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVCBSEJBNTSX3IM7KOUVSJTZOMWQHAVCNFSM6AAAAABLEJC6WSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJTG44DGNBWGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thanks, @rh10hd! And I'm glad you got it working, @JSFLJ! I've now created a new version that relies on Homebrew installation through Alfred's 'Resolve Dependencies' feature. That should therefore rid any problems with architecture!' There is one caveat, though: I'm not sure if this version too requires manual removal of quarantine. Could you test this beta to see if it works automatically, once you've run 'Resolve Dependencies', or if you get an error because If this version also requires manual removal of quarantine, I'm not sure I'll implement it, as there'll be too many installation steps. |
(I’m not an English native speaker, some words and grammars might be used incorrectly, so I hope this does not cause you any misunderstanding or inconvenience.) Hi @vegardinho . Wow! Thanks for updating the workflow!! I became the lucky one to have a try on the new beta version😉I installed it as soon as I received your mail, it worked well on my Mac! I didn’t even resolve the dependencies in Alfred preferences. So I think the problem is that the Alfred doesn’t have the access to Bluetooth. Giving Alfred the permission to control the Bluetooth is not mandatory so lots of people would not do that lol. Nevertheless I have to say that I’ve installed Moreover, in the course of using this workflow, I’ve met 2 bugs. First, when I Second, when I tried to Regardless, the new beta version is BRILLIANT even though there are a few minor issues. Thanks again! |
Thanks for the feedback, @rh10hd! Maybe you're right that allowing Alfred to manage bluetooth is sufficient! Still, I'm not comfortable ruling out the possibility of it not being enough – besides, what about the notifcator binary? I assume Alfred is already allowed to post notifications? The fact that you were able to run homebrew-blueutil without allowing it specifically, though, is promising! I think I've fixed the bug related to the confirmation, using your suggestion. Try installing the beta below to see if you still get the same problem behavior as before. The device names is not really something I've changed in the latest releases, so it's not really related to this beta. If you continue to get old names, feel free to create a new issue! If you are able to first reproduce the error on a different computer, to rule out your computer being the error source, that would be great – but feel free to post the issue either way. |
Thanks!! @vegardinho |
Now pushed v4.2. Closing this issue. |
I opened blueutil and notificator as shown in the installation guide, but I still can not interface with my bluetooth devices through alfred.
The text was updated successfully, but these errors were encountered: