Bugs
Done

In-app update to 0.1.5 fails repeatedly on macOS ("could not be installed"), no error details or logs

The in-app prompt offered "Version 0.1.5 is ready to be installed." Clicking Update always ended with "Update failed – Version 0.1.5 could not be installed." Try again failed the same way every time.

  • Previous version: [0.1.x]
  • macOS 27 Golden Gate, Apple Silicon

A dev sent me a direct link to the 0.1.5 .app file. Replacing the app manually worked fine.

2 Comments

Sign in to comment

D
Den
Den·4 days ago

Hi, thanks for the report, and sorry for the trouble with the update.

We found the cause. macOS sometimes runs an app from a temporary, read-only location instead of from where it's stored. This happens when the app was opened from Downloads or straight from the disk image (.dmg). From that location Any can't replace itself, so the update failed the same way every time you clicked Try again. Replacing the app by hand worked because moving it into Applications takes it out of that temporary location.

What we're changing in an upcoming release:

  • If Any is running from a place where it can't update itself, it won't try and fail. It will ask you to move Any to the Applications folder instead.
  • When an update does fail, we'll now record the actual reason, so problems like this are much quicker to diagnose.

Since you've already replaced the app manually and it's now in Applications, future updates should install normally. If you ever see this error again, make sure Any is in the Applications folder and opened from there.

Thanks again for reporting it. This led us straight to the fix.

S
smellythief·5 days ago(edited)

Also, this feedback board itself has a bug:
Editing this post fails to save, the Save button does nothing. The UI also stays in edit mode with no error shown. I tried in Chrome, Zen and Safari. The save server function returns HTTP 200 with a $TSR/Error body:

Failed query: select … from post_comments where post_id = $1 and principal_id ≠ $2 and deleted_at is null limit $3
params: 01a0f423-b675-7663-a3d5-d2941282249d, principal_01m3fy2tf3ecst2djt96fr064x, 1

Possible cause: principal_id is passed as a prefixed ID (principal_…) while post_id is a plain UUID. If the column is UUID-typed, that comparison would fail. This probably affects every author's edits.

Edit: Comments can be edited though...