Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/10/2021 in all areas

  1. So you’ve just updated to the new buggy shininess released by Apple. Congrats! But thread lightly. At all costs, you should avoid installing a beta macOS version on a machine with data you can’t afford to lose or waste a day resetting. In the course of your beta trial, you’ll bump into bugs and general issues. Some will be related to Alfred and Workflows, which will make you tempted to jump on this forum for help. Stop! Then wait. Ask yourself “is this a bug I should be reporting?” The closer to WWDC21, the likelier the answer is “no”. The overwhelming majority of bugs at this point will sort themselves out. And they are inconsistent. At the time of writing there have been two comments from users on the new macOS beta: one said Alfred worked, the other that it didn’t. At this point the new beta is so unstable we can’t even rely on a consistent experience between users, meaning no way to isolate and understand problems—effort spent in that direction wold be wasted. Avoid drowning the forum with unactionable bug reports. In general, if you don’t have enough knowledge or skill to figure out the cause of the problem, you should refrain from installing a beta OS. Please avoid filling but reports if that’s the case. Or file them at Apple, since it’s their end causing the breaks and giving them feedback is the point of installing their beta OS. So when should you start reporting general Alfred bugs? Look at the bug reports subforum. Do you see a “macOS 12.0 Monterey Bugs & Issues” section? If not, it’s too soon. What about Workflows? You should follow the same logic. If a Workflow stops working, either the developer will know because they are using the beta, or they won’t know and won’t be able to fix it anyway because they are not on the beta. There are exceptions to the above, but few. If you do make a bug report, please make sure to follow the instructions. Do that, and everyone will be more willing to look into your issue sooner and help get you sorted. Thank you. Have fun with the new features.
    2 points
  2. No idea how I missed this! Thank you! Great work!
    1 point
  3. Don't use Run NSAppleScript. It does weird things. Use Run Script with Language = /usr/bin/osascript (AS) instead.
    1 point
  4. deanishe, thank you for the suggestion. I attempted the following in a NSAppleScript: on alfred_script(q) do shell script "rm -r '/Users/path/to/folder/'" with administrator privileges end alfred_script and got the following error. NSAppleScriptErrorAppName = "Alfred 4"; NSAppleScriptErrorBriefMessage = "rm: /Users/path/to/folder/: Operation not permitted"; NSAppleScriptErrorMessage = "rm: /Users/path/to/folder/: Operation not permitted"; NSAppleScriptErrorNumber = 1; NSAppleScriptErrorRange = "NSRange: {22, 160}"; } ...which led me down the path of searching for "operation not permitted" and another post of yours about "macOS is basically a UNIX system with Cool Apple Shit layered on top." 🙂 ...which, after confirming that Alfred has Full Disk Access (which it did), when I switched to using Run Script with /bin/bash allowed it to work without sudo. So, I think I found my solution with your previous solution...and a little bumping around in the dark on my end. 🙂 Thank you again and have a great day.
    1 point
  5. Same issue here!! I set up a lot of short texts, so it's very annoying for me. In other Apps, like Google Chrome for example, go to the menu bar and choose "Edit > Substitutions > Show Substitutions > Text Replacement" and deselect Text Replacement. This could turn off the text replacement feature. But, there' no menu bar show with alfred's input box! I can find the same menu with mouse right click on it, and can be disable temporary, but it won't save! Text replacement will re-enable after reboot. Can't find a solution....
    1 point
×
×
  • Create New...