hugo/Gotcha
1
0
Fork 0
Code Issues 5 Pull Requests Actions 1 Packages Projects Releases 1 Wiki Activity

Document AltStore-only iPhone deployment

Browse Source
This commit is contained in:
Georg Bauer
2026-08-15 11:56:50 +02:00
parent 8e2feac18e
commit 2f5269a6e9
3 changed files with 32 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
AGENTS.md
View File

@@ -130,19 +130,29 @@ iPhone (currently `xcrun simctl boot "iPhone 17 Pro"`) and open Simulator.
CoreSimulator access may require running `xcodebuild` and `simctl` outside the
workspace sandbox.
## Post-issue release deployment
## Post-issue release handling
After an issue is verified, committed, pushed, commented on, and closed, deploy
After an issue is verified, committed, pushed, commented on, and closed, handle
the completed version according to the code it changes:
- For CLI changes, build `gotcha-cli` in release mode and install the resulting
`gotcha` executable in `~/.local/bin/` so the command is available on `PATH`.
- For iOS app changes, install the completed app on the currently paired iPhone.
- For iOS app changes, validate the completed app in the simulator. Never install
an Xcode-run or otherwise development-signed build on a physical iPhone; this
would replace the correctly signed AltStore PAL installation.
- Physical iPhone installs and updates must use the complete AltStore PAL release
process: create and validate a distribution-signed Release archive, submit it
for notarization, publish the accepted Alternative Distribution Package and
source update, then install or update Gotcha through AltStore PAL.
- Publishing an AltStore PAL release is not an automatic per-issue step. Perform
it only when the user explicitly requests and authorizes release publication.
- The Gitea crate is shared by the CLI and iOS app, so changes to that crate also
require installing the completed app on the paired iPhone.
require simulator validation and inclusion in the next authorized AltStore PAL
release.
A purely CLI change does not require an iPhone deployment. If an issue changes
both release surfaces, perform both deployments.
A purely CLI change does not require iOS validation. If an issue changes both
release surfaces, install the CLI release and validate the iOS app in the
simulator.
## Generated build data