Claude
7fe1dfe42d
Without an explicit scheme, xcodebuild's auto-scheme only reports the app target's settings — which made the Mac mini builder skip the share extension when generating provisioning profiles, causing the export to fail with "GiteaIssueShare.appex requires a provisioning profile." Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Gitea Issue
iOS share-extension for filing issues to a self-hosted Gitea instance straight from a screenshot.
Take screenshot → Share → Gitea Issue → pick repo, title, notes → submit. The screenshot is uploaded as an attachment and embedded inline in the issue body.
Architecture
Two targets in one Xcode project, sharing an App Group + Keychain:
- GiteaIssue (
com.treytartt.GiteaIssue) — container app, settings + help only - GiteaIssueShare (
com.treytartt.GiteaIssue.Share) — share extension that does the real work - App Group:
group.com.treytartt.GiteaIssue(cached repo list, recents) - Keychain group:
$(AppIdentifierPrefix)com.treytartt.GiteaIssue(base URL, token)
iOS 26.0 minimum. Signing team V3PF3M6B6U.
Layout
GiteaIssue/ Container app (settings + help)
GiteaIssueShare/ Share extension UI
Shared/ Models, Keychain, Settings, GiteaClient, RepoCache
project.yml xcodegen spec — regenerate with `xcodegen generate`
Build
xcodegen generate
xcodebuild -project GiteaIssue.xcodeproj -scheme GiteaIssue \
-destination 'generic/platform=iOS' build
Deploy (ad-hoc)
Push to admin/GiteaIssue on Gitea, then trigger the Mac mini builder at
http://Treys-Mac-mini.local:3090 against the git URL. Builder ships the IPA
to https://appstore.treytartt.com for OTA install.
First-time setup on device
- Install via Safari from
appstore.treytartt.com - Open the Gitea Issue app, set base URL + personal access token (
reposcope) - Tap Save & test connection — confirms login and pre-fetches the repo list
- From now on: Photos → screenshot → Share → Gitea Issue