I upgraded to Mojave (10.14.3) recently to resolve a spotlight indexing issue, and now none of my Automator services work in Fluid-created apps.
Background: I have over a dozen automator services which take selected text as input and I use them in a series of apps I created (as a user of Fluid.app, which turns websites into apps). The main issue is a series of Fluid apps I created for a bioinformatics cluster-interface web app called galaxy. The galaxy web app doesn't let you have multiple browser windows open to different projects because changes in 1 window affect other windows. I worked around this by creating 3 galaxy apps with Fluid, which allows me to have 3 activate concurrent bioinformatics projects open (on different desktops).
After upgrading to Mojave, all my automator services will no longer run on selected text in those apps. I get an error saying basically that "Run Applescript" (a section of the automator workflow) does not have permission to send "Apple events" to "System Events.app".
I have added the galaxy apps I had created using Fluid to accessibility & "Full Disk Access" in the security and privacy system prefs, but it still errors out.
I learned from an apple tech support guyb that the app in which I'm trying to run the service needs to be code-signed by an apple recognized developer. And of course it's not signed. I, as an end user, created the app. I don't even see a paradigm by which end-user-created apps will ever have the ability to be code signed, thus allowing a user to run *their* automator services in an app they created.
My question is, is this correct? Is there no avenue for a user-created app (e.g. using an app-creating tool like Fluid which essentially creates a copy of a browser that defaults to a user-entered website)?
Forgive me for my ignorance, but shouldn't the user have the ability to use *their* automator workflows they created (explicitly to use in any app) in *any app*? Or at the least, shouldn't they be given the opportunity to allow this to work and thus grant the requisite permission? I understand that it's not a good idea to grant access to an unsigned app, but Fluid.app is signed itself and the user has created an app for their own personal use. Shouldn't they be able to run their workflows in it? Perhaps a workflow should have its own app entity on ths system and it can be granted the permission. Any app in which the workflow is used can be asked for its selected text and give it to the workflow app that's requesting it...
Obviously, I don't know the inner workings of all this, but regardless, it looks like there is not a way, given the new sandboxing in Mojave to run a service in truly "any app".