Skip to content

Stop offering AltStore an older version of itself as an update - #1797

Open
izaankml wants to merge 1 commit into
altstoreio:classicfrom
izaankml:fix/altstore-self-update-check
Open

izaankml wants to merge 1 commit into
altstoreio:classicfrom
izaankml:fix/altstore-self-update-check

Conversation

@izaankml

@izaankml izaankml commented Sep 13, 2026

Copy link
Copy Markdown

Problem

A Classic build newer than the source's latest AltStore entry lists that older entry under Updates. A classic build is 2.3.3 and the default source lists 2.2.2, so My Apps offers 2.2.2 as an update. StoreApp.setVersions takes the source's first supported version for AltStore's own entry without comparing it to the installed version. Marketplace builds already compare, but only inside #if MARKETPLACE.

Fix

Apply the Marketplace comparison to every non-notarized build and drop the Classic-only fallback. Older or equal entries are no longer offered, newer ones still are. Notarized builds are unchanged.

Testing

On device with a 2.3.3 build and the default source, the "AltStore 2.2.2" row under Updates is gone after sources refresh.

Classic builds took the source's latest supported version as AltStore's
update candidate without comparing it to the installed version, so a
build newer than the source's latest entry was offered that entry as an
update: a self-built 2.3.3 was shown the source's 2.2.2 under Updates.
Apply the rule marketplace builds already use: only a supported version
whose version number is at least the installed one qualifies. Notarized
builds keep their existing behaviour of never self-updating.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant