Search Alfred Workflows (Alfred 4)

[raguay.customct]

17 hours ago, Acidham said:

I would say that would be an enhancement request for Alfred Preferences  @Andrew

 

I never discovered a WF where info.plist was malformed and I expected that Alfred will throw an error in case  info.plist is corrupt. 

 

So far we don't know what exactly caused the issue. Can you ( @raguay.customct) figure out which workflow caused the issue and share the WF with me for further investigation?

You can figure it out in case the enabled workflow cannot be found by alf.

 

It might take a while since I have around 80 workflows on my system.

[Acidham]

@raguay.customct Added log output when corrupted WF was found. Please install version 0.7.3 and open debugging console in Alfred. The WF path contains the corrupted WF  will be written to the log: 

[09:07:23.292] STDERR: Search Alfred Workflows[Script Filter] Corrupt Workflow found, path: /Users/acidham/Dropbox/Alfred/Alfred.alfredpreferences/workflows/user.workflow.9E01D57B-1985-48BA-96CF-BBACDD1219A3/info.plist

 

[bk161124]

In the Workflow, in "Applescript handling Alfred WF UI:" the Applescript code reads as follows:

on run argv
	set theQuery to item 1 of argv
	tell application "System Events"
		keystroke space using control down
		delay 0.1
		keystroke theQuery
	end tell
end run

Here 

keystroke space using control down

should be variable because people tend to have different Alfred triggers 😊

[deanishe]

The script wants replacing with this, tbh:

 

on run argv

    tell application id "com.runningwithcrayons.Alfred" to search (item 1 of argv)

end run

Edited July 7, 2019 by deanishe

[Acidham]

Thanks for heads up, you are totally right! Fixed in version 0.8...

[raguay.customct]

On 6/11/2019 at 2:19 PM, Acidham said:

@raguay.customct Added log output when corrupted WF was found. Please install version 0.7.3 and open debugging console in Alfred. The WF path contains the corrupted WF  will be written to the log: 

[09:07:23.292] STDERR: Search Alfred Workflows[Script Filter] Corrupt Workflow found, path: /Users/acidham/Dropbox/Alfred/Alfred.alfredpreferences/workflows/user.workflow.9E01D57B-1985-48BA-96CF-BBACDD1219A3/info.plist

 

Sorry, I seamed to have missed this. It's my Pollen workflow. You can download it from my workflows repository on GitHub:  https://github.com/raguay/MyAlfred

 

The workflow loads and runs fine. I've removed it and re-installed it and your workflow still says it's in error. Not sure how to fix it other than recreating it.

 

Edited July 11, 2019 by raguay.customct

[Acidham]

Thx @raguay.customct 

 

I installed your Pollen workflow and what when I debug my workflow it seems that plist reader fails here with: 

xml.parsers.expat.ExpatError: not well-formed (invalid token): line 826, column 12

But I cannot find an invalid token in info.plist of Pollen 😕

[raguay.customct]

That's what I thought too. Not sure what is happening.

[Acidham]

it seems that Call External "EditFile" is causing this issue. When I remove that step it works. 

[raguay.customct]

2 hours ago, Acidham said:

it seems that Call External "EditFile" is causing this issue. When I remove that step it works. 

 

Okay, that is suppose to go to My Editor Workflow to call the editor I am using to edit the configuration file. Now, the alf command doesn't show a bad workflow. I had forgotten that I had changed the name of the workflow and I haven't needed to edit those files recently. But, why would calling a workflow that has been renamed as a XML parse error?

[Acidham]

I have no idea!

 

i played around a bit wit other bundle ids e.g. self.something and it works. With your ID it fails 😕

[deanishe]

5 hours ago, Acidham said:

Thx @raguay.customct 

 

I installed your Pollen workflow and what when I debug my workflow it seems that plist reader fails here with: 

xml.parsers.expat.ExpatError: not well-formed (invalid token): line 826, column 12

But I cannot find an invalid token in info.plist of Pollen 😕

 

You sure there are no invisible characters in there?

[Acidham]

45 minutes ago, deanishe said:

 

You sure there are no invisible characters in there?

 

I quickly checked it but I was not able to find anomalies. I assume it must be somewhere in xml structure but I did not run further investigations. Anyhow @raguay.customct "fixed" it

[Acidham]

new version 0.9 is now showing available keyboard shortcuts in quicklook help

Edited November 26, 2019 by Acidham

[ItsJaky]

I'm not a coder, I installed the workflow for alfred 4 

"

[18:31:30.384] Logging Started...

[18:31:32.751] Word Search[Script Filter] Queuing argument 'l'

[18:31:32.758] Word Search[Script Filter] Script with argv '(null)' finished

[18:31:32.759] ERROR: Word Search[Script Filter] Code 127: /bin/bash: python: command not found

[18:31:32.940] Word Search[Script Filter] Queuing argument 'lo'

[18:31:32.946] Word Search[Script Filter] Script with argv '(null)' finished

[18:31:32.947] ERROR: Word Search[Script Filter] Code 127: /bin/bash: python: command not found

[18:31:33.052] Word Search[Script Filter] Queuing argument 'lov'

[18:31:33.056] Word Search[Script Filter] Script with argv '(null)' finished

[18:31:33.057] ERROR: Word Search[Script Filter] Code 127: /bin/bash: python: command not found

[18:31:33.136] Word Search[Script Filter] Queuing argument 'love'

[18:31:33.202] Word Search[Script Filter] Script with argv '(null)' finished

[18:31:33.205] ERROR: Word Search[Script Filter] Code 127: /bin/bash: python: command not found"

please help

[Acidham]

Did you install python 3 ? 

 

What is python3 -V telling you when you execute it in terminal ?

[vitor]

8 hours ago, Acidham said:

What is python3 -V telling you when you execute it in terminal ?

 

You can’t rely on that. The PATH is the Terminal is unlikely to be the same that Alfred uses. Note @ItsJaky has a python error, not python3. The likeliest explanation is that they’re on an old version of the Workflow.

[Acidham]

@vitor Yep seems you are right. But OneUpdater is implemented and should keep the WF fresh. 

 

@ItsJaky Please update the WF: https://github.com/Acidham/search-alfred-workflows/releases/tag/v2.0.0  and try again. 

[vitor]

4 hours ago, Acidham said:

But OneUpdater is implemented and should keep the WF fresh.

 

Not if the Workflow breaks in a way OneUpdater will never trigger because its object can’t be reached, which is the case here.

[Acidham]

On 5/1/2022 at 11:59 AM, vitor said:

 

Not if the Workflow breaks in a way OneUpdater will never trigger because its object can’t be reached, which is the case here.

 

Correct forgot that little piece