You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to sync my alfred between two macs. I setup my new macbook air today using the official guide: https://www.alfredapp.com/help/advanced/sync/ but your workflow seems to be buggy on my macbook air (it works fine in my mac mini).
I cannot do:
timezone add $city$
timezone edit (won't open any editor)
timezone move (won't open anything)
GIF recording of the timezone add behavior - both macs have the aame path. I am using Synology Drive for syncing.
Any idea whats wrong? I already tried to reinstall alfred and re-do the sync but this workflow continues to not work and I can't seem to find where the timezones.txt is configured so I can verify the path its using is the same Synology Drive path.
The text was updated successfully, but these errors were encountered:
It looks like Synology Drive when it syncs the alfred settings - may not properly sync permissions. I assume this based on another workflow that started failing and the error was more explicit about "chmod +x" permissions missing - looking insde the alfredpreferences folder the permissions seemed correct.
It wasn't until I manually uninstalled the workflow and re-added again that it started working. I moved my alfred settings to iCloud drive - re did the setup and it seems to be working now.
I'm trying to sync my alfred between two macs. I setup my new macbook air today using the official guide: https://www.alfredapp.com/help/advanced/sync/ but your workflow seems to be buggy on my macbook air (it works fine in my mac mini).
I cannot do:
GIF recording of the
timezone add
behavior - both macs have the aame path. I am using Synology Drive for syncing.Any idea whats wrong? I already tried to reinstall alfred and re-do the sync but this workflow continues to not work and I can't seem to find where the timezones.txt is configured so I can verify the path its using is the same Synology Drive path.
The text was updated successfully, but these errors were encountered: