CLI (dayone2) not working – 2024.9

  • Unknown's avatar
    andreclaassen · Member ·

    Please give us an ETA. We are waiting now 3 Month for a fix for this error. The Commandline-Tool is unusable at this state.

  • Unknown's avatar
    helper-lilly · Member ·

    Hi @andreclaassen,

    I understand your frustration and apologize for the inconvenience. Our developers are actively investigating the issue with the Commandline-Tool. Unfortunately, we do not have an ETA for the fix at this moment. Thank you for your continued patience and understanding.

  • Unknown's avatar
    agilezone5091 · Member ·

    Just add my name to the list.

    This is crazy. This bug has been here for a long time and can’t be that hard to fix.

    Very disappointed in Day One.

  • Unknown's avatar
    helper-james · Member ·

    Thank you for your feedback, @agilezone5091. We have added your report to the ticket.

  • Unknown's avatar
    mp2mmcrckm · Member ·

    So this has been a known issue for over 4 months now, with no fix, no ETA, no substantive updates. My monthly subscription is starting to feel like a waste of money, and I’m starting to feel like a sucker for keeping it. Disappointing and discouraging.

  • Unknown's avatar
    djpadz · Member ·

    Well, I managed to get dayone2 working. Here’s how I did it. You’ll need an Apple developer ID to do this. If you don’t have one, using a self-signed certificate may work, but I haven’t tried it, so no promises.

    Short version:

    codesign -s <your ID> -f /usr/local/bin/dayone2

    The problem is that the signature for dayone2 is messed up. If you run Console.app, you’ll see something like this when you try to run dayone2:

    Error loading /Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit (69):  dlopen(/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit, 0x0109): tried: '/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit' (code signature in <69E50666-61F2-33BC-97F7-6CD0EDFCF2A0> '/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/Versions/A/CLIKit' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Volumes/Preboot/Cryptexes/OS/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit' (no such file), '/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/CLIKit' (code signature in <69E50666-61F2-33BC-97F7-6CD0EDFCF2A0> '/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/Versions/A/CLIKit' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/Applications/Day One.app/Contents/Frameworks/CLIKit.framework/Versions/A/CLIK<…>

    The fix is to replace the signature.

    Honestly, it seems silly that this problem has existed for so long; it’s something that can be remedied with a single command.

  • Unknown's avatar
    andreclaassen · Member ·

    Thank you so much 🙏🙏🙏.

    I will try it out.

    P.S: It is a shame that Day One not fix it by themselves.

  • Unknown's avatar
    andreclaassen · Member ·

    got it working with a self signed certificate. I have stored my certificate in the “system” key chain.

    I needed to run codesign with root rights:

    sudo codesign -s <your ID> -f /usr/local/bin/dayone2

  • Unknown's avatar
    helper-james · Member ·

    Hi @djpadz! Thanks so much for sharing. We have also found the same, and we are working on an update to resolve this.

    P.S: It is a shame that Day One not fix it by themselves.

    Thanks, @andreclaassen. I understand your frustration. We do our best to prioritize issues according to impact and severity. We were able to work on this recently and will have a fixed released in version 2024.16, coming to the Mac App Store within the next couple of weeks.

  • Unknown's avatar
    mtnzxwqvwp · Member ·

    I came here having the same issue as a subscriber. After reading through the thread, I am waiting for that release 2024.16 to see if it fixes the isue.

  • Unknown's avatar
    seanandrewrose10 · Member ·

    Is this still broken? I can’t get it to work.

  • Unknown's avatar
    helper-lilly · Member ·

    Hi @seanandrewrose10,

    We’ve recently addressed this issue, and the fix will be included in our next update, version 2024.16.
    Please let us know if you continue to have issues after the update.

  • Unknown's avatar
    djpadz · Member ·

    Confirmed that the update has hit the app store and appears to work. Thanks!

  • Unknown's avatar
    helper-lilly · Member ·


    Glad to hear it, @djpadz! Thanks for the update.

  • Unknown's avatar
    larryjclai · Member ·

    I still have issue with CLI tool.

    I try to see if CLI work and enter this code

    dayone2 -h

    return:

    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")%

    I checked the Dayone path is correct.

    echo $DAYONE_APP_PATH
    /Applications/Day One.app

    How can I solved it? My app version is 2024.16

  • Unknown's avatar
    helper-james · Member ·

    Hi @larryjclai. Are you updated to version 2024.16 on the Mac App Store?

    See here: https://dayoneapp.com/guides/settings/locating-the-version-number-of-day-one/.

    This update should resolve the issue for you.

1 2
  • The topic ‘CLI (dayone2) not working – 2024.9’ is closed to new replies.