Cassady

Happy to report that following the latest update to Ventura 13.4, which coincided with my spelunking around in the hot-mess that is the new System Settings, I managed to re-enable Alfred permissions, and all is now working again. I know this will require more work on your part -- but a possible suggestion to consider (if there isn't already one??), is to pop up a blog-post/how-to article with screenshots of where all the possible Alfred permissions toggle buttons might be in the new System Settings. Given that the latter is not very user friendly in the first place, it now takes a fair amount of patience/persistence in finding all the places those toggles might be found in. Fairly certain the root of my issues was one that was unchecked (or at least, had become unchecked) -- but even though I found it literally a few minutes back, I am already fairly certain I would need to hunt for it again, since it was not at all where I would have expected to find it.

Hello @Vero — any suggestions? The problem persists. I ran the Terminal command (and it confirmed successful). Upon restarting Alfred, I was however NOT asked to re-enable permissions. Toggled the switch in System Settings manually again, and inside the Alfred prefs. Regardless, no joy. Running Alfred 5.1 [2134], macOS Ventura 13.3

Just to close this – as per suggestion of @giovanni – deleted everything (including /caches) related to the ISYN workflow, and reinstalled. All working again.

Ah – thanks, this at least confirms what happened. I used Box to sync my Alfred prefs – and Box had to be "reset" yesterday, given some unknown issue. That must have caused the issue. I will see what I can manage, in terms of sorting this out.

I have a similar "permission denied" error that cropped up today, also on one of @Deanishe 's workflows [see here ]. @bongobong Did you get your's resolved?

Anyone else having any issues with this workflox? Box.app suddenly threw up an error, which I fixed via Terminal – this after I had done a reboot. And then, this workflow suddenly stopped working. Feels to me as if something was done by my updating to 13.3 Ventura last(?) week, that this morning's reboot triggered. Debugging has the following error: Code 126: /Users/b****g/Library/Caches/com.runningwithcrayons.Alfred/Workflow Scripts/380E648B-86A3-4C72-BC5D-4092F0FB1A03: line 2: ./isyn: Permission denied @giovanni, any ideas on how to "give permission" again? Flicking "Full access" off and on under Settings/Privacy & Security doesn't work.

THANK YOU! All fixed and running!

Anyone else have this workflow broken after updating to Ventura? Increasingly convinced I haven't ticked a "permissions setting" somewhere – but struggling to work all of that out on the new OS. So, figured I would check here first. Debugger shows the following: [16:16:45.897] Logging Started... [16:16:50.765] Student Number Lookup (New)[Script Filter] Queuing argument '(null)' [16:16:50.856] Student Number Lookup (New)[Script Filter] Script with argv '(null)' finished [16:16:50.862] ERROR: Student Number Lookup (New)[Script Filter] Code 1: xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

Thank you SO much for doing this! I had given up, and rolled my own manual solution using the built-in list filter – but the original was always so much better. This is now working as it was, and I couldn't be happier. Thanks again!

Many thanks – I should have thought to dig around a bit in there. Will give the transfer a go, and see what comes of it. EDIT: Hmmm. Seems to only contain PList preference files, that presumably link back to other folders for the actual content of the prior clipboards. Will be a little bit cautionary in my transfer approach, to ensure I don't cause any undoable results...

Hello all, I rely on Alfred's clipboard history each and every day as an integral part of my workflow(s), and it really is jarring not having it at hand, so to speak! Just transitioned to a new MBP – and whilst I have managed to get everything set up and moved over, with all workflows and settings etc. intact – I am (obviously) missing my clipboard history, and built-up over the rolling 3-months prior, on my old MBP. Is there a way to copy the clipboard history over to the new machine, to have that "history" available to me now again?

Hi Vero – appreciate the assistance. The post linked to above, so kindly put together, also links back to an Alfred help post, on reinstalling Python 2 – as found here. Unfortunately, following those instructions does not work, when trying the install through Terminal. It fires back (on my side, at least), the following error: python-build: use zlib from xcode sdk BUILD FAILED (OS X 12.3 using python-build 20180424) Inspect or clean up the working tree at /var/folders/zn/jy0jnfks28qfrfgphswgrcn40000gn/T/python-build.20220405173019.34079 Results logged to /var/folders/zn/jy0jnfks28qfrfgphswgrcn40000gn/T/python-build.20220405173019.34079.log Last 10 log lines: checking MACHDEP... darwin checking EXTRAPLATDIR... $(PLATMACDIRS) checking for --without-gcc... no checking for --with-icc... no checking for gcc... clang checking whether the C compiler works... no configure: error: in `/var/folders/zn/jy0jnfks28qfrfgphswgrcn40000gn/T/python-build.20220405173019.34079/Python-2.7.18': configure: error: C compiler cannot create executables See `config.log' for more details make: *** No targets specified and no makefile found. Stop. ln: /usr/local/bin/python: File exists So, kind of stuck back at square one, since presumably without a version of Python 2 that the various workflows depend on, nothing in the initial post, is going to work as it should. Oh, and apologies for dropping this all in here – but unfortunately did not seem to have a way of responding in the Alfred help blog-post.

Still rocking an Intel – but Silicon on the horizon in the next few weeks.

Ah – thank you for clarifying difference between Python 2 and 3! And huge thanks for offering assistance – sadly, still running into issues. The support doc Homebrew installation of Python 2 failed, with the following message: BUILD FAILED (OS X 12.3 using python-build 20180424) Inspect or clean up the working tree at /var/folders/zn/jy0jnfks28qfrfgphswgrcn40000gn/T/python-build.20220317095201.71946 Results logged to /var/folders/zn/jy0jnfks28qfrfgphswgrcn40000gn/T/python-build.20220317095201.71946.log So, seemingly back to square 1. Will try and get clarity on what might be going wrong with the above.

It was working like a charm on Alfred 4 over the past several months – until today. Finally updated to macOS Monterey last night, and that seems to have broken it. Log throws out the following: Code 126: /Users/goldfish/Library/Caches/com.runningwithcrayons.Alfred/Workflow Scripts/100A1AA1-3884-4F6B-92C9-6B59DE8CD8E9: ./isyn: /usr/bin/python: bad interpreter: No such file or directory REALLY hope I can get this working again – this workflow is so powerful, and saves me so much time... [EDIT]: Ok. So, clearly I've been living under a rock. Did not realise that Python 2(.7?) was no longer part of macOS Monterey – and seemingly needs to replaced with Python 3 as the "new" default. And, assuming I understand things correctly, the above error log is simply saying that the /isyn workflow was trying to find usr/bin/python at its usual location – but now nothing is there, hence the error. So I presumably have to "simply" install Python 3 in the /usr/bin/python directory, and all should go back to working as before? Which means –– I need to spend time working through this thread! Yay me!