raguay.customct 49 Posted June 11, 2019 Share Posted June 11, 2019 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. Link to post
Acidham 61 Posted June 11, 2019 Author Share Posted June 11, 2019 @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 Link to post
bk161124 1 Posted July 7, 2019 Share Posted July 7, 2019 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 😊 Link to post
deanishe 1,372 Posted July 7, 2019 Share Posted July 7, 2019 (edited) 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 Link to post
Acidham 61 Posted July 7, 2019 Author Share Posted July 7, 2019 Thanks for heads up, you are totally right! Fixed in version 0.8... Link to post
raguay.customct 49 Posted July 11, 2019 Share Posted July 11, 2019 (edited) 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 Link to post
Acidham 61 Posted July 11, 2019 Author Share Posted July 11, 2019 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 😕 Link to post
raguay.customct 49 Posted July 11, 2019 Share Posted July 11, 2019 That's what I thought too. Not sure what is happening. Link to post
Acidham 61 Posted July 11, 2019 Author Share Posted July 11, 2019 it seems that Call External "EditFile" is causing this issue. When I remove that step it works. Link to post
raguay.customct 49 Posted July 11, 2019 Share Posted July 11, 2019 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? Link to post
Acidham 61 Posted July 11, 2019 Author Share Posted July 11, 2019 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 😕 Link to post
deanishe 1,372 Posted July 11, 2019 Share Posted July 11, 2019 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? Link to post
Acidham 61 Posted July 11, 2019 Author Share Posted July 11, 2019 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 Link to post
Acidham 61 Posted November 26, 2019 Author Share Posted November 26, 2019 (edited) new version 0.9 is now showing available keyboard shortcuts in quicklook help Edited November 26, 2019 by Acidham cands 1 Link to post
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