Possible Slogger-related bug in DayOne2: please confirm
shartf opened this issue · comments
Hello,
sorry to bother, but I want to ask for a confirmation of a possible bug in DayOne2. Since it was updated to v.2.0.3, Slogger cannot add any entries to DayOne2. Interestingly enough, it runs without any error and reports that entries were added. So, either they have changed the parsing algorithm or it is a simple bug. Can anyone confirm it?
I'm seeing exactly the same thing.
I've sent a bug report to DayOne team. Will post the feedback here, if there is any.
I'm seeing the same thing, I've still got it running, but I've also turned to IFTTT as they've just added a Day one channel. So I've turned on most of my Slogger plugins in IFTTT and it's been working fine. I'll keep my slogger running and hopefully they can get it fixed soon.
I think I'm seeing the same thing. For those of you having the issue, can you open up the folder by running this command:
open "$HOME/Library/Group Containers/5U8NS4GX82.dayoneapp2/Data/Auto Import/Default Journal.dayone/entries"
Then run Slogger again and see if you see the entries appear, and then disappear from this folder. This is what I'm seeing. Once the files disappear (which I assume means it's being imported into DayOne, they don't actually appear in the app.
I think, there is nothing we can do on our side. I've submitted a bug report to DayOne Team more then a week ago but received no answer yet. I've tried to write posts directly via the CLI, too -- with the same negative result. So, I guess, they just broke their import completely in the last update.
I've got a message from the DayOne Team, they know about issues with CL and are working on it.
The Known Issues page lists this issue and says it will be fixed with the forthcoming 2.0.5 release of DayOne. (Current version is 2.0.4.) http://help.dayoneapp.com/known-issues/
The 2.0.5 update is out and it fixed auto importing for me.
Confirmed, @chrisxero!