the solution : Ad-hoc self-sign the debug binary so its identity stays stable between runs, even after rebuilds pointing to the same path
dev's avatar dev
now i know why ! The binary lives in ~/Library/Caches/buzz-target-arm64/debug/ — a debug build, sitting in a cache folder that gets wiped/rebuilt often. It's unsigned (debug builds aren't code-signed by default). Every time you (or just dev) rebuild it, Cargo produces a new binary with a different hash, even though the file path is identical. macOS Keychain ties "Always Allow" trust to that binary identity — so a new hash = new app as far as Keychain is concerned = prompt resets. View quoted note →
View quoted note →