Some In-App Updates Shipped an Incomplete App. 1.7.1 Fixes It

Most bugs announce themselves. A crash, a red banner, a button that does nothing. This one was quieter, and worse, because it shipped to people who had done nothing wrong. They updated the app from inside the app, the way the app itself asked them to, and the update delivered a copy with two important pieces missing.

What actually broke

The local image engine, the piece that generates pictures on your own GPU, could arrive missing. Ask her for an image and the app reported that the local engine was not installed, with no button to download it, because that button only appears when the engine is present. It was a loop with no exit.

The same incomplete update could also drop the component that runs your local model. She would sit there with a model selected and never produce a word. If you happened to run your own Ollama, you might never have noticed, because your own setup filled the gap.

Why it happened, plainly

The update package was assembled from the app before the local engines were placed inside it. The result shipped at about 70 MB where the full installer is 245 MB. The difference is not compression. The difference is the missing engines.

The .dmg installer was never affected. This was specific to the in-app update path, which is exactly why it stung: the people most likely to hit it were the people already using the app and updating it the normal way.

What 1.7.1 does

The fix applies itself the moment you update to 1.7.1. If images or local chat stopped working after an update, updating to 1.7.1 restores them. And the packaging step was changed so the update is built from the finished, signed app, with a hard stop: the build refuses to complete if any engine is missing from it. The same mistake cannot ship again in the same form.

Nothing else changed. No new features, no moved settings, and your characters, chats, licence and downloaded models are untouched.

Back to news