altstoreio / altstoreio/AltStore
No such command 'mounter' on MacOS 26 developer beta 4
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 14.4k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
I am currently using macOS 26 Developer Beta 4 to develop my app, and I’m also using the same Mac for phone development.
I have done my best to use the Xcode beta’s Python located at /Applications/Xcode-beta.app/Contents/Developer/usr/bin/python3 to install the required versions of pymobiledevice3==2.30.0 and construct==2.10.69. Although Xcode’s Python is version 3.9.6, I encounter errors such as:
The process 'altjit' failed with code 1.
The process 'python3' failed with code 2.
Error: No such command 'mounter'.
Initially, I faced the error:
The process 'altjit' failed with code 1. ❌ Unable to mount personalized Developer Disk.
However, I haven’t encountered this specific error again. But when I try to enable JIT on Windows, the issue "The process 'altjit' failed with code 1. ❌ Unable to mount personalized Developer Disk" reappears.
I have tried installing earlier versions of both pymobiledevice3 and Xcode, but I still can’t resolve the issue.
who can help meeeeeeeeeeeeeeeeeee
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on macOS 26 Developer Beta 4 using the Xcode Python path and the reported pymobiledevice3 and construct versions. Trace the altjit invocation and the missing mounter command; done means identifying whether the failure is in the environment or AltStore workflow and documenting a confirmed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, python, swift
- Domain
- mobile-dev, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100