-
|
Hello Taskwarrior team, I just did the switch from 2.6.2 to 3.0, and it went through without a hitch. Then I set up the taskchampion-sync-server and did my first sync, also without issue. But then I realised that I had committed the sync.encryption_secret line in the taskrc to my dotfiles repo. So I deleted the taskchampion-sync-server DB file and changed the CLIENT_ID env variable to a new ID and restarted the server. And in the server logs I'm seeing: Is there some kind of reset I would need to execute after switching the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hm, I got the issue somewhat solved. I went into the local taskchampion sqlite DB and removed the entry in the After that, the sync went through without issue. Would there have been a simpler solution which doesn't involve SQL queries? |
Beta Was this translation helpful? Give feedback.
The error you saw is actually just a bug -- GothenburgBitFactory/taskchampion-sync-server#154. It's fixed in the latest taskchampion-sync-server version.