v0.6.0-beta24
If Minutiva Private has been quitting the moment you open it, this is the build that fixes it. Please download it directly from the link above — the app can’t update itself when it closes before it finishes starting.
What went wrong
Three builds — beta21, beta22 and beta23 — were signed without the permission the app needs to reach your private iCloud area. Nothing was wrong with the code that was written; the final step of our own release script quietly removed it while packaging. Everything that doesn’t involve iCloud kept working, which is why it went unnoticed.
Then macOS began treating that missing permission as fatal rather than ignorable, and the app started closing during startup instead of running without sharing.
What it means for you
Your recordings, transcripts, summaries and speaker names were never at risk. They live in files on your Mac and nothing in this touched them. The app failed before it opened, not while it was working.
Sending meetings to your other Mac has not worked since beta20. If you turned it on and nothing ever arrived, that was this — not your setup, and not something you did. It works from this build onward.
So it can’t happen again
Our release process now refuses to publish a build unless it can confirm, on the finished app itself, that the permissions are present. The bad builds were correct everywhere a person would have looked — the source, the settings, the build log — and wrong only in the packaged result. That’s the thing now being checked.
Auto-update
Existing beta channel testers get this within 24 hours. Or trigger now: Minutiva Private → Check for Updates…