CLI (dayone2) not working – 2024.9
-
The dayone2 CLI is not working, this is eactly like the previous post https://forums.dayoneapp.com/forums/topic/day-one-cli-no-longer-working-with-2024-6-mac-app/.
Here’s a snippet of my CLI output:
$ dayone2 -h
Could not find needed ‘CLIKit’ in searchPaths ((
“/Applications/Day One.app/Contents/Frameworks”,
“/Applications/Day One.app/Contents/Frameworks”,
“/Applications/Day One.app/Contents/Frameworks”
))
This is needed for CLI utility to run. You can set environmentalvariable DAYONE_APP_PATH to the Day One app to help utility find it.(Example: export DAYONE_APP_PATH=”/Applications/Day One.app”)$
$ echo $DAYONE_APP_PATH
/Applications/Day One.app$ ls -al /Applications/Day One.app/Contents/Frameworks
total 0
drwxr-xr-x 7 root wheel 224 Apr 26 09:36 .
drwxr-xr-x 11 root wheel 352 May 9 10:17 ..
drwxr-xr-x 5 root wheel 160 May 9 10:17 CLIKit.framework
drwxr-xr-x 5 root wheel 160 May 9 10:17 DOCore.framework
drwxr-xr-x 5 root wheel 160 May 9 10:17 DOIntents.framework
drwxr-xr-x 5 root wheel 160 May 9 10:17 DOWidgets.framework
drwxr-xr-x 5 root wheel 160 May 9 10:17 DOXKit.framework$ file /Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit
/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64:Mach-O 64-bit dynamically linked shared library arm64]
/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit (for architecture arm64): Mach-O 64-bit dynamically linked shared library arm64 -
Hi, @frankstutz! Although we still can’t give a timeline for when this issue will be fixed, I’ve made sure to add your case to our report that’s tracking this issue.
-
Please give us a timeline, since not able to use CLI makes DayOne very useless to me.
Thank you, André
-
Hi, @andreclaassen!
Unfortunately, we can’t provide a specific timeline for when this issue will be resolved. I apologize for the inconvenience this is causing you. I’ve added your case to our report tracking this issue. -
I have the exact same problem. I’ve had it for a while now. First time I encountered it some months ago I thought I was just being dumb. But now I’m seeing it’s a known issue and DayOne isn’t doing anything about it. Disappointed, because I’m a premium subscriber.
-
-
Hi @fidelnamisi7e1287c030 and @paulnielan. This issue is on our list to fix. I have also added your reports to the open issue. Thank you.
-
Also having the same issue. I use this cli in one of my projects. Hoping if more report it, it’ll get bumped up the timeline. 🙂
dayone2 -h
Could not find needed ‘CLIKit’ in searchPaths ((
“/Applications/Day One.app/Contents/Frameworks”,
“/Applications/Day One.app/Contents/Frameworks”
))
This is needed for CLI utility to run. You can set environmentalvariable DAYONE_APP_PATH to the Day One app to help utility find it.(Example: export DAYONE_APP_PATH=”/Applications/Day One.app”)% -
Hi @impomales
Thank you for reporting this issue, I’ve added your case to our report tracking this issue. -
I’m also having this issue – just switched back to DayOne and trying to import some MD files using the CLI (https://gist.github.com/dnsbty/b9e1b8788b7c1f88878910442a87b861)
Getting this same error and wanted to file it so hopefully it can be fixed soon.
Could not find needed ‘CLIKit’ in searchPaths ((
“/Applications/Day One.app/Contents/Frameworks”,
“/Applications/Day One.app/Contents/Frameworks”
))
This is needed for CLI utility to run. You can set environmentalvariable DAYONE_APP_PATH to the Day One app to help utility find it.(Example: export DAYONE_APP_PATH=”/Applications/Day One.app”)% -
Hi @ellenchisa,
Thank you for your report. I’ve passed it along to our development team for further investigation and resolution. -
Today I opened Day One and I found a brand spanking new interface. I must admit I shook my head thinking, “I wonder how many users asked the dev team for interface improvements, versus how many asked them to fix the CLI.” I’d love to know how the dev team prioritizes updates.
-
Hi @namworldzerodrafts! When it comes to feature requests, our developers consider features for every release based on the number of requests we receive for that feature. Customer feedback is a very helpful tool as we work to prioritize new features.
-
I am also waiting for this fix, since 2024-05-22.
I know the engineering team is busy and work by priority. But, this problem is a quality issue. It’s a simple packaging issue, not a software bug.
Obviously working usecase was broken, and impacted customer experience. Although DayOne offers reasonable subscription fee, still we are paid customers and working feature was broken. Shouldn’t it be high priority to fix?
-
Hi @rchung725,
I understand your perspective. Your feedback about the urgency of this fix has been acknowledged and forwarded to our engineering team. We appreciate your patience and understanding. -
I am experiencing the same issue after much trouble shooting on my end. I have nothing really to add that other folks haven’t already shared.
-
This is such a groundbreaking issue and should be part of the most basic integration text of the team. When will we get a fix?
-
Version after Version incoming, but this bug stays unfixed. The CLI is a significant interface for me. Please fix it!
-
I just updated 2024.12.1 (1566)
Still seeing this problem. Is this requiring some cleanup? I expect that install script should do it, but if there is a workaround, please share. Here is my error.
% export DAYONE_APP_PATH="/Applications/Day One.app" 1031:√ Resources % dayone2 Could not find needed 'CLIKit' in searchPaths (( "/Applications/Day One.app/Contents/Frameworks", "/Applications/Day One.app/Contents/Frameworks", "/Applications/Day One.app/Contents/Frameworks" )) This is needed for CLI utility to run. You can set environmentalvariable DAYONE_APP_PATH to the Day One app to help utility find it.(Example: export DAYONE_APP_PATH="/Applications/Day One.app")% -
@jsatk @andreclaassen @rchung725
As you know, this has been reported to our developers. However, it will likely take some time to address this particular issue, which unfortunately I don’t have an exact timeframe on.
Thanks for your patience and understanding in the meantime!
- The topic ‘CLI (dayone2) not working – 2024.9’ is closed to new replies.
Day One Forums 