Summary
On macOS Apple Silicon, updating lark-cli from v1.0.61 to v1.0.68 succeeds, but the CLI then hangs at startup. Even lark-cli --version produces no output and does not exit.
Environment
- macOS 15.7.7 (24G720)
- Apple Silicon / arm64
- Node.js v26.3.0
- Installed through npm (
@larksuite/cli)
- Working version before update: v1.0.61
- Failing versions tested: v1.0.67 and v1.0.68
Steps to reproduce
lark-cli update --json
lark-cli --version
Actual behavior
The update command completes and npm shows the target package version installed, but lark-cli --version hangs indefinitely with no stdout or stderr. Other commands such as lark-cli auth status --json --verify behave the same way.
Restarting the Mac did not resolve it. Reinstalling v1.0.67 and v1.0.61 after the failed update also initially showed the same startup hang until stale processes were cleared; a clean v1.0.61 installation is the only version that has been reliably usable.
The launched native binary is .../node_modules/@larksuite/cli/bin/lark-cli (Mach-O arm64, code signature verifies successfully).
Expected behavior
After a successful update, lark-cli --version should print the version promptly and other commands should run normally.
Related issue
Possibly related to #165 (macOS arm64 binary startup failure), but this manifests as an indefinite hang rather than an immediate exit code 137.
I can provide more diagnostics if there is a preferred trace/log command.
Summary
On macOS Apple Silicon, updating
lark-clifrom v1.0.61 to v1.0.68 succeeds, but the CLI then hangs at startup. Evenlark-cli --versionproduces no output and does not exit.Environment
@larksuite/cli)Steps to reproduce
Actual behavior
The update command completes and npm shows the target package version installed, but
lark-cli --versionhangs indefinitely with no stdout or stderr. Other commands such aslark-cli auth status --json --verifybehave the same way.Restarting the Mac did not resolve it. Reinstalling v1.0.67 and v1.0.61 after the failed update also initially showed the same startup hang until stale processes were cleared; a clean v1.0.61 installation is the only version that has been reliably usable.
The launched native binary is
.../node_modules/@larksuite/cli/bin/lark-cli(Mach-O arm64, code signature verifies successfully).Expected behavior
After a successful update,
lark-cli --versionshould print the version promptly and other commands should run normally.Related issue
Possibly related to #165 (macOS arm64 binary startup failure), but this manifests as an indefinite hang rather than an immediate exit code 137.
I can provide more diagnostics if there is a preferred trace/log command.