// Publish the native iOS app to TestFlight from this repo. Use when archiving/exporting/uploading builds, bumping versions, checking App Store Connect processing status, or fixing common upload failures.
| name | ios-publish |
| description | Publish the native iOS app to TestFlight from this repo. Use when archiving/exporting/uploading builds, bumping versions, checking App Store Connect processing status, or fixing common upload failures. |
Publish workflow for apps/ios (HighswarmFeed) in this turborepo.
apps/ios/HighswarmFeed.xcodeprojcom.joelhooks.highswarm.feedN7L54A44YXjoelhooks@gmail.comapps/ios/scripts/deploy-testflight.shFrom repo root:
pnpm ios:testflight
This runs:
generic/platform=iOS)ExportOptions.plist)xcrun altoolBefore first upload:
com.joelhooks.highswarm.feedsecurity add-generic-password -a "joelhooks@gmail.com" -s "AC_PASSWORD" -w "<app-specific-password>"
If Apple ID belongs to multiple providers, set provider public ID:
export ASC_PROVIDER_PUBLIC_ID="c6caf075-f2be-4200-9b9a-f2d2c677f9e4"
Bump build before each new upload:
/usr/libexec/PlistBuddy -c "Set :CFBundleVersion <N>" apps/ios/HighswarmFeed/Info.plist
Version keys live in:
apps/ios/HighswarmFeed/Info.plist
CFBundleShortVersionStringCFBundleVersionAfter upload, check status with delivery UUID:
xcrun altool --build-status \
--delivery-id "<delivery-uuid>" \
--provider-public-id "c6caf075-f2be-4200-9b9a-f2d2c677f9e4" \
-u "joelhooks@gmail.com" \
-p @keychain:AC_PASSWORD \
--output-format json
Typical statuses:
VALID_BINARY (uploaded and valid)BETA_INTERNAL_TESTING (available for internal testing)Symptoms:
Fix:
apps/ios/HighswarmFeed/Assets.xcassets/AppIcon.appiconset/Icon-1024.png existsapps/ios/project.yml includes:
ASSETCATALOG_COMPILER_APPICON_NAME: AppIconapps/ios/HighswarmFeed/Info.plist includes:
CFBundleIconName = AppIconSymptoms:
Fix:
com.joelhooks.highswarm.feedapps/ios/project.yml and regenerate.Build and maintain the native iOS client inside this turborepo (XcodeGen, SwiftUI, WebSocket feed). Use when creating/updating the iOS app, wiring turbo tasks, or documenting iOS workflows.
Deploy the atproto-agent-network project. Two separate Cloudflare Workers must be deployed independently — the network worker (API + agents) and the dashboard worker (highswarm.com). Use when deploying changes, fixing the dashboard, or updating agent configs.
Cloudflare Durable Objects patterns for agent state. Use when implementing agent DOs, WebSocket handling, hibernation, storage API, alarms, or DO-to-DO communication. Triggers on Durable Object, DO state, WebSocket server, hibernation, agent persistence.
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
Pi agent runtime integration for Cloudflare. Use when implementing the agent loop, tools, extensions, session trees, or multi-provider LLM calls. Triggers on Pi, agent runtime, tool calling, streaming, session tree, extensions, self-extending agent.
D1 database patterns for encrypted agent records. Use when implementing schema, storing/querying encrypted records, migrations, or working with the records table. Triggers on D1, database, schema, records table, SQL, encrypted storage.