Broken in macOS Catalina

[maltsev]

It seems that this workflow doesn't work in macOS Catalina anymore.

@iansinnott, @nikitavoloboev can you check that, please? I don't plan to upgrade my OS version yet since Catalina doesn't support 32-bit apps.

[nikitavoloboev]

I don't play to upgrade Catalina due to its insane security popups & sVim not working.

[iansinnott]

@maltsev I also have no plans of upgrading. I don't generally do macOS platform dev so I don't have a spare box lying around to upgrade instead of my main computer :/

Sorry, for now the recommendation is do not upgrade. Obviously we'll probably all have to upgrade sooner or later but my hope is that they will sort things out with Catalina by then.

---

As an aside, Catalina seems like such a rushed, unstable, ill-conceived release on apples part. Even if it was stable, those security popups mentioned by nikitavoloboev offer such poor UX. It's troubling. Historically this is out of character for them, but the latest iOS release wasn't great either. I'm worried for the platform.

[nikitavoloboev]

https://github.com/deanishe/alfred-sublime-text/issues/20#issuecomment-539578934

Above solution may fix the problem.

[deanishe]

I've added the workaround to the AwGo wiki.

It currently says the same as the comment @nikitavoloboev linked. I will update it if/when a simpler solution is found.

Historically this is out of character for them

The awful UX is, but really buggy OS releases are par for the course these days. They just don't care about quality any more. Instead of working on the OS till it's in pretty good shape and then releasing it, they just throw whatever they've got out the door come September, regardless of what state it's in.

[iansinnott]

Update: I now have a computer running Catalina (10.15.1) and so far everything is working as expected. I didn't have to do any additional setup either. Perhaps the latest public Catalina build addressed some issues.

I've only been up and running with the new OS for about 30 minutes though, so take this with a grain of salt.

[dacasine]

Works for me.

What I did to avoid the notarization was to open the package once installed, simply double-click on alfred-maestre, authorize the app and execute once.

After that, everything is working fine.

[deanishe]

I didn't have to do any additional setup either.

I believe Catalina automatically allows binaries you've compiled yourself.

[iansinnott]

I believe Catalina automatically allows binaries you've compiled yourself.

Fair point. It's been long enough now that I don't remember if I compiled the workflow myself when I installed it, but it's possible that's the case.

[lukaskawerau]

The way to make this work:

1. Go to Alfred > Workflows
2. Select the workflow, right-click, "Open in Finder"
3. Right-click the binary file, click "Open"
4. Apple will ask you to confirm, since it can't verify there's no malware in this
5. Done

[jrasanen]

I can confirm that method Lukas described works. You only have to do this once.

[slyfoxgh]

The way to make this work:

1. Go to Alfred > Workflows
2. Select the workflow, right-click, "Open in Finder"
3. Right-click the binary file, click "Open"
4. Apple will ask you to confirm, since it can't verify there's no malware in this
5. Done

Thank you. This worked.

[gridwalk]

Note- if the binary file is missing after installing the workflow you can change the file name of AlfredMaestro.alfredworkflow to AlfredMaestro.zip, unzip it and you will find the binary in there. Copy the binary into the folder described in lukaskawerau's working solution and follow those steps.

[lkuty]

Working flawlessly in 10.15.6. I installed from sources.

[deanishe]

I installed from sources.

Yeah, if you build it yourself, Catalina won't complain. The problem is that it has a nasty habit of simply deleting unsigned binaries you downloaded.