nikivi Posted October 9, 2019 Share Posted October 9, 2019 (edited) Got this issue on my workflow. I am not on v10.15 but users of my workflows and I suppose others too will get this prompt on calling an external trigger or keyword. What should they do to get around it? I found this issue online when googling for error. Is there anything @Andrew and Alfred can do to remove this friction? Edited October 9, 2019 by nikivi Link to comment Share on other sites More sharing options...
deanishe Posted October 9, 2019 Share Posted October 9, 2019 This solution was posted to one of my Go workflows: https://github.com/deanishe/alfred-sublime-text/issues/20#issuecomment-539578934 It's not very straightforward, though. nikivi 1 Link to comment Share on other sites More sharing options...
vitor Posted October 9, 2019 Share Posted October 9, 2019 2 hours ago, nikivi said: Is there anything @Andrew and Alfred can do to remove this friction? No, but you might by opening the Feedback Assistant and complaining to Apple. On WWDC they claimed they wouldn’t stop you from running software you want, but these prompts get really close. They’re going against their own advice from an older WWDC already, so I wouldn’t trust this won’t get worse. Link to comment Share on other sites More sharing options...
baa76 Posted November 2, 2019 Share Posted November 2, 2019 Hi there, I was getting the same errors which were quite frustrating. Adding Alfred here has seemed to work for me. deanishe 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now