Repository navigation
Conversation
6063de6 replaced AltSign-Dynamic with AltSign-Static for AltServer and AltJIT but left the product references on both targets. Xcode re-adds the framework links from those references whenever the workspace is opened, so both products end up linked, ldid is built as a standalone dylib, and the build fails with undefined OpenSSL symbols.
…provide anisette data On macOS 26 and later, AOSKit's retrieveOTPHeadersForDSID: returns an empty dictionary unless the caller holds private entitlements, so AltServer fails with "could not retrieve anisette data value machineID" (altstoreio#1751). When both AOSKit and the Mail plug-in fail, AltServer now fetches anisette data from a remote anisette server using the same v3 protocol AltStore uses on-device. Servers come from AltStore's published list, the first working server is remembered, and the provisioned identity is stored in Application Support so Apple sees the same machine across launches. Two defaults control the behavior: - AnisetteServerURL pins a specific server - DisableRemoteAnisette turns the fallback off
Author
|
Closing in favor of fafd76e, which shipped in AltServer 1.8.1. I tested the official 1.8.1 build on macOS 27.0 (M4 Pro) with an iPhone 14 Pro on iOS 27.0: the anisette libraries downloaded on first use, and both installing AltStore and refreshing from the device worked. Local generation is a nicer fix than depending on a third-party server, thanks for getting it out quickly. Two leftovers in case they're useful:
|
rileytestut
pushed a commit
that referenced
this pull request
Oct 21, 2026
Add RemoteAnisetteDataFetcher, based on the remote anisette fetcher from #1806 by Nick Clyde, so AltServer can get anisette data from an anisette v3 server instead of generating it locally. - Fetches client_info and user_agent from /v3/client_info and only accepts servers whose client_info identifies Windows. - Provisions a dedicated identity through /v3/provisioning_session. The URL bag lookup uses a Mac client info; the provisioning requests use the server's Windows client info. The identity is stored in RemoteAnisetteWindows/identity.json, separate from AnisetteKit's. - Re-provisions once when the server reports -45061 and supports resynchronizing with X-Apple-I-MD-DATA. - Defaults to https://ani.jkcoxson.com; can be overridden with the AnisetteServerURL user default. Adds remoteServerUnavailable, remoteServerInvalidResponse and provisioningFailed errors to AnisetteError.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #1751 (
AltServer could not retrieve anisette data value "machineID") on macOS 26 and later by falling back to a remote anisette server when AOSKit can't provide anisette data.Root cause
On macOS 26+,
AOSUtilities.retrieveOTPHeadersForDSID:returns an empty dictionary unless the caller holds private entitlements, so AltServer never getsX-Apple-MD-Mand every install or refresh fails. The Mail plug-in path fails the same way.What this does
When both AOSKit and the Mail plug-in fail, AltServer fetches anisette data from a remote anisette server using the same v3 protocol AltStore already uses on-device in "AltServerless" mode. The client is a port of
FetchAnisetteDataOperation.swiftfrom the AltStore target, with the on-device specifics swapped for macOS equivalents:cdn.altstore.io/file/altstore/altstore/anisette-servers.json. The first server that works is remembered inpreferredAnisetteServerURLso the same provisioned identity keeps being reused.adi.pbare stored in~/Library/Application Support/com.rileytestut.AltServer/AnisetteIdentity.jsonwith mode 0600. If a server rejects the cachedadi.pb, AltServer re-provisions once.com.apple.akd/1.0, matching c558994.URLSessionWebSocketTaskasync APIs andRegexBuilder.Two defaults control the behavior, in the same style as
JITTimeout:AnisetteErrorgains three codes (remoteServerUnavailable,remoteServerInvalidResponse,provisioningFailed) with user-facing messages that name the server and a recovery suggestion that mentions the override.Project file cleanup (separate commit)
6063de6 replaced
AltSign-DynamicwithAltSign-Staticfor AltServer and AltJIT but left the product references on both targets. Xcode re-adds the framework links from those references whenever the workspace is opened, so both products get linked,ldidis built as a standalone dylib, and the build fails with undefined OpenSSL symbols. The first commit removes the two stale references. It stands on its own if you'd rather take it separately.Design choices worth your review
C02LKHBBFD57placeholder the AOSKit path and the iOS client already use.Testing
Tested on an Apple Silicon Mac running macOS 27.0 with an iPhone on iOS 27.0.
Not yet exercised: the
DisableRemoteAnisetteandAnisetteServerURLoverrides.Note on building: Xcode 27 refuses the project's
MACOSX_DEPLOYMENT_TARGET = 11.0(minimum is now 12.0). I built withMACOSX_DEPLOYMENT_TARGET=13.0on the command line and left the project setting alone for you to decide.Related: #1770 solves the same problem with a bundled Linux VM and also adds an
AnisetteServerURLoption. This PR is the lighter-weight route and reuses the on-device client instead.AI usage disclosure
Claude Fable 5.1 (Anthropic) assisted with this change. It reviewed the community workaround at kimziro/altserver-macos27-anisette-fix, ported the on-device v3 client to AltServer, diagnosed the
ldidlink failure and the stale project references, and drafted this description. I reviewed the code, built it, and ran the tests listed above on my own hardware (MBP M4 Pro on macOS 27, iPhone 14 Pro on iOS 27).