Title
Soundflow logged in but not working
What do you expect to happen when you run the script/macro?
I currently can't add new key command triggers - after a system update, it seems Soundflow isn't quite running with all the permissions it needs, and after a fresh install of Soundflow that is still the case
Are you seeing an error?
What happens when you run this script?
When i try to record a key command, soundflow doesn't recognise the key inputs, despite soundflow being activated as a valid app in System Prefs > Privacy > Input Monitoring
How were you running this script?
Other
How important is this issue to you?
5
Details
{
"inputExpected": "I currently can't add new key command triggers - after a system update, it seems Soundflow isn't quite running with all the permissions it needs, and after a fresh install of Soundflow that is still the case",
"inputIsError": false,
"inputWhatHappens": "When i try to record a key command, soundflow doesn't recognise the key inputs, despite soundflow being activated as a valid app in System Prefs > Privacy > Input Monitoring",
"inputHowRun": {
"key": "-MpfwoFyZNOpBC3X5xGI",
"title": "Other"
},
"inputImportance": 5,
"inputTitle": "Soundflow logged in but not working"
}
Source
sf.ui.proTools.appActivate();
Links
User UID: ViQPEeIY8QVwQ40kgvaM3cNtbH03
Feedback Key: sffeedback:ViQPEeIY8QVwQ40kgvaM3cNtbH03:-N014idJoO-5N8xE7o6S
Linked from:
- Ventura Upgrade. Soundflow unresponsive
- All of my applescripts macros are broken after recent update.
- Sound Flow - Log In Issue - Security & Privacy
- Keep getting no connection to backend issue
- Cannot open SoundFlow on Sonoma
- SF stops reacting to keyboard input for unknown reasons
- Custom Surface has a substantial proportion of Buttons non functional
- updated to monterey and now steam decks aren't even recognized by usb hub
Christian Scheuer @chrscheuer2022-04-19 16:33:54.891ZThank you Pete for these details!
Before we dive into more troubleshooting, I have one theory which is that this could be related to our code signing process. There was a certificate that expires this month (they're valid 5 years at a time). This shouldn't cause the app to not run, but it's possible the Security & Privacy settings get confused if the certificates are mismatched between older and newer SF versions.
To test this hypothesis, please do these steps in order (every step):
- Quit SoundFlow entirely (SF icon by clock -> Quit).
- Run this in Terminal:
pkill -9 SoundFlow - Remove SoundFlow from Applications and clear Trash
- Run this in Terminal:
tccutil reset All org.soundflow.sfsx - Restart the computer
- Install SF 5.1.0 from my.soundflow.org
- You should be prompted to grant permissions
- See if things work better
If this doesn't help, it would be great if you could make a screen recording showing this - perhaps seeing things in action would help us understand where things are going wrong.
Christian Scheuer @chrscheuer2022-04-19 16:34:37.519ZHere's another related thread which seemed to indicate there was an issue if using SoundFlow on multiple macOS accounts at the same time (same computer, multiple macOS logins):
- In reply tochrscheuer⬆:PPete Watson @Pete_Watson
This seems to have solved the problem, thanks!