sulliops

Well the only reason I say it’s an M1-specific bug is that it worked fine on my Intel MacBook running 11.1 until I migrated to my new laptop yesterday. But I’ve encountered a couple other small issues with Big Sur on M1, including DaisyDisk not opening without forcing Rosetta (in a near-identical fashion to Alfred), so I’m willing to chalk it up to a Big Sur bug. In any case, just figured I’d share how I fixed it. Hopefully macOS 11.2 is a bit more stable, I’ve heard it’s all about bug fixes. Not brave enough to install the beta on my brand new machine, whereas I normally would go ahead and try it.

I had the same problem starting today with my new M1 MacBook Air, and ultimately I discovered the problem (for me, at least) lies in running the app natively; I fixed it by forcing both Alfred and Alfred Preferences to run under Rosetta 2. Here's how: Open your Finder and navigate to Applications, find Alfred and right-click > "Get Info". Check the box that says "Open using Rosetta". Right-click on the Alfred app again, then click "Show Package Contents". Navigate to Content > Preferences. Right-click on the Alfred Preferences app, select "Get Info", and check the box that says "Open using Rosetta". Launch Alfred. This won't be of any use to anyone encountering this issue on an Intel Mac, but I figured I'd share my solution since this is the only forum thread about the issue I've seen. Hope this helps!