Closed macmeister closed 1 year ago
Yeah, you are right, this should be a syncing issue.
Uninstall the workflow, and then reinstall it. (Run osetup etc again) That should fix it.
Also, you have to run osetup once on every device you are using the workflow on
Thank you! Is syncing possible, or not at all with this workflow? I will try your suggestion on both machines, but not sure if it will let me (with the syncing). I can post results…
Syncing works just fine, I sync with 3 devices without any issues.
I assume that dropbox just got stuck with the sync somehow. Therefore, the wipe and clean re-install.
Thank you for clarifying your success, Chris! Will keep trying. I removed and reinstalled plugins on both Macs, however the second Mac is always the problem. It now works on Mac 2, but not Mac 1 (since I started fresh on it this time). Maybe it's because it's a shared dropbox folder. Are you suggesting removing and re-installing Dropbox too? It is fairly fresh on both Macs.
Allow full disk access for Dropbox may have fixed it. Will post accordingly. ;) EDIT: Maybe not, as I keep going back and forth with 1 machine working at a time. I get one working, then the other fails. I did also notice that it wants to update inside Alfred, but I'm trying not to since the newest version isn't in the Alfred repository apparently. I've been clicking update and I think it's rolled me back a couple times (to 4.0.2), so sticking with the github version (4.0.3) to see how it will do.
This is apparently an ongoing issue likely with Dropbox file permissions and Alfred, and still unresolved with this workflow, including others. If I find a solution, I will post it here. And if someone has a solution, please share. I'm testing other workflows with similar functionality as a possible substitute. Thanks for any tips! At least I'm not the only one: https://www.alfredforum.com/topic/19572-workflows-not-working-after-syncing-to-dropbox/
Bug Description
This is definitely related to Dropbox syncing workflows, however I'm not sure if it can be cured. With a little research with other scripts it might be easily curable and I wanted to let @chrisgrieser know just in case. Hopefully this is the right place.
After syncing workflows, it will continue to work locally on the original Mac, but when I get on the other one, I get the attached error when running it with the command oo anyway.![Image 2023-08-10 at 10 28 15 PM](https://github.com/chrisgrieser/shimmering-obsidian/assets/3847742/ab0bf0c6-f558-44dd-895c-93dfc0e89b65)
I'm hoping maybe one of these posts will allow some insight or suggestions for a possible workaround? https://github.com/ShogunPanda/alfred-chrome/issues/5 Could it be as easy as adding this somewhere?
!/bin/bash
I found the above through this as well: https://www.alfredforum.com/topic/19902-unable-to-run-external-script-from-workfolder-couldnt-posix_spawn-error-8/
Relevant Screenshot
No response
To Reproduce
Debugging Log
Workflow Configuration
These same settings work on the original machine, I even reviewed and resaved them on the synced machine with same error. Could be just a dropbox limitation, however other workflows appear to be working fine.
Version & System Information
Last working version
No response
Make sure you have done the following
o…
main search does not work, I made sure that I haven't changed any of the default settings of the Metadata-Extractor. Furthermore, I have tried rerunningosetup
and it still does not work.oupdate
command to manually update the metadata..obsidian
(About → Advanced → Override config folder).