v3 takes less than 1.5s on my MacBook Air 2017. On my MacBook Pro 2022, v3 is twice as fast as v2 (0.5s against 1s).
Could you post the output of Alfred debugger for v1.2 and v1.3? Just hide your serial number.
I just released a new version of the workflow with some fixes and support for Apple Silicon.
It's not slow on new Macs but it's possible to make it faster by caching the machine icon generated by the getMacIcon.applescript. Unfortunately my AppleScript skills are a bit outdated so I would be happy if @vitor or someone else could submit a PR.
It confirms the issue is related to pip not installing PyCryptodome binaries for the ARM architecture. I can’t do anything about it, since it’s a PyCryptodome issue that seems to have already been reported.
In any case, the workflow will only prompt you to install PyCryptodome if you try to decrypt a PDF file encrypted with AES or RC4 standards.
I'm still curious to know what @giovanni did to get it to work on his ARM Mac.
Could you please download this PDF file and run the Decrypt file action on it? The password is asdfzxcv.
In the process you should be prompted to install PyCryptodome. You can accept it.
@pankajsz @zeitlings guys, now I see I may have made a stupid mistake. Could you delete the workflow, download the latest version from GitHub and install it again? Please, let me know if it works or not.
It seems to be related to this PyCryptodome issue.
Curiously, I did some tests with @giovanni a couple months ago and he managed to get it working on his ARM Mac. Maybe he was using Rosetta?
I don’t have an ARM Mac, btw.
It's already included.
Any chance you have moved from an Intel Mac to an ARM Mac? Or maybe syncing Alfred between machines with both architectures? What Python version are you running?
I would advise you to delete the workflow and install it again. If it doesn't work I will need the input files that you can send me via PM.