Skip to content

mac-v0.9.6 release ships with version="dev" + menubar shows "--" for all metrics (data loader not wired) #210

@willau95

Description

@willau95

After running codeburn menubar (and re-confirmed with codeburn menubar --force), the installed ~/Applications/CodeBurnMenubar.app reports its version as "dev" and shows -- for every metric in the dropdown.

Reproduction

$ codeburn menubar --force
Looking up the latest CodeBurn Menubar release...
Downloading CodeBurnMenubar-0.9.6.0.zip...
Unpacking...
Launching CodeBurn Menubar...
  Ready. /Users/.../Applications/CodeBurnMenubar.app

$ defaults read ~/Applications/CodeBurnMenubar.app/Contents/Info CFBundleShortVersionString
dev

$ defaults read ~/Applications/CodeBurnMenubar.app/Contents/Info CFBundleVersion
dev

Symptom

The menubar app launches successfully (adhoc-signed Universal binary, runs as PID), but every field in the menubar dropdown shows -- (no Today/Month cost, no calls, no cache hit %, no projects).

Diagnostic — the app isn't reading the cache

lsof against the running CodeBurnMenubar process shows it does not open ~/.cache/codeburn/* nor ~/.claude/projects/*:

CodeBurnM 7006 user  txt    REG  ... /Users/.../Applications/CodeBurnMenubar.app/Contents/MacOS/CodeBurnMenubar
CodeBurnM 7006 user  txt    REG  ... /Library/Preferences/Logging/.plist-cache.*
CodeBurnM 7006 user  txt    REG  ... /System/Library/CoreServices/SystemVersion.bundle/...
(no codeburn cache, no claude transcripts)

CLI is fine on the same machine

The CLI works perfectly with the same data:

$ codeburn status
  Today  $23.46  56 calls    Month  $58.28  142 calls

And ~/.cache/codeburn/daily-cache.json is 30KB and freshly updated, so the data layer is healthy.

Hypothesis

The asset CodeBurnMenubar-0.9.6.0.zip published in release mac-v0.9.6 (2026-05-03) appears to be a dev/staging build that:

  1. Was built without bumping the CFBundleShortVersionString and CFBundleVersion constants from "dev" to "0.9.6".
  2. Ships without the data-loader wired in (or wired against a dev-only endpoint), so it never reads the local cache that the CLI populates.

A clean release build that reads the same ~/.cache/codeburn/daily-cache.json the CLI writes should fix both symptoms.

Environment

  • macOS: 26.2 (Apple Silicon)
  • codeburn (npm): 0.9.6
  • Installation: npm install -g codeburn then codeburn menubar --force
  • App path: ~/Applications/CodeBurnMenubar.app
  • App signature: adhoc, Universal (x86_64 + arm64)

Happy to run any extra diagnostics if helpful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions