Hi, I’d like to transfer BarCuts’ settings accross two macs (same icloud, same version). As far as I can tell there’s no sync via icloud, nor export settings option, right?
As an alternative to that - I noticed ~/Library/Preferences/co.zottmann.BarCuts.plist and I already keep .plist files in git for Rectangle and iTerm, and it’s noisy but works 
So would it be safe to share this plist config file across systems?
Cheers and thanks for the amazing work @czottmann
Copying that file to another machine would work for transferring the initial settings only but sharing/syncing won’t because it contains the permission data for accessing the Shortcuts folder, and that is signed by macOS by device, and therefore not transferrable.
Same goes for the actual meat (i.e., metadata for all the workflows) which is stored in a SQLite database (~/Library/Application Support/BarCuts/). It’s not made for use by more than one macOS at the same time. It references bits and pieces in the Shortcuts DB which differ between machines, even Macs using the same Apple Account.
Sorry.
Any plans to work on this? I have my desktop and my laptop, and having to re-add all the actions is a pain. I feel like this wasn’t an issue when there was the tagger action, any way we can have the option to resurface that?
Any plans to work on this? I have my desktop and my laptop, and having to re-add all the actions is a pain. I feel like this wasn’t an issue when there was the tagger action, any way we can have the option to resurface that?
The situation hasn’t changed — for any given workflow, Shortcuts’ own internal ID for that workflow can be different between machines, even on the same Apple Account. Since BarCuts relies on those IDs, transferring/ sharing the BarCuts DB would not be stable, and will lead to problems. For example, you configure several workflows in BarCuts on one machine, and they work, but it’s likely not all of them would still be configured on another Mac because for some reason, Shortcuts did something to their internal IDs.
I don’t know why that is, since Shortcuts is effectively a black box.
And the Tagger action is not a viable solution w/r/t workflows that are also supposed to run on iOS, because they will break on mobile since on iOS, there’s no Tagger action. (Plus some other internal reason why I removed it.)
Sorry.
With the Tagger action, I just use the Device action. If Device=Mac, run Tagger Action; otherwise, do nothing. It worked fine.