Welcome to Holeberry v1.0.2!
Warning
This is a hot fix release — the previous CI-deployed version had broken Keychain logic, so this release changes how credentials are stored. Since I don't have a paid Apple Developer account yet, releases are ad-hoc signed, which means the new Keychain logic will ask you to approve the "Holeberry wants to access Keychain" prompt for each Pi-hole instance you have, on every new update.
If you already have instances set up, you'll be asked to re-authenticate in the Settings window once, so your credentials get properly stored.
What's fixed
- Adding a server no longer fails with
errSecMissingEntitlement(#2). The connection always worked — saving your password to the Keychain was what broke. Credentials are now stored in a way that works on ad-hoc-signed builds. - No more half-created servers. A failed save no longer leaves a server registered without its password.
- Servers without a saved password now show "No saved credential" with a Re-authenticate button, instead of a confusing "unreachable / Retry / Fix" loop.
- The edit sheet's Submit button no longer stays disabled when you change the URL or enter a credential.
What you need to do
- After updating: open Settings, and for each instance that shows "No saved credential", click Re-authenticate and enter your password once. It will be stored properly from then on.
- On future updates: approve the "Holeberry wants to access Keychain" prompt when it appears (one per instance). This is a one-time-per-update prompt caused by ad-hoc signing, and it goes away once releases are signed with a paid Developer account.