Documentation

What CapWrap adds to the repo

Every file CapWrap may write: Capacitor wrap, init workflow, and the native store pipeline.

CapWrap treats your GitHub repo as the source of truth. It adds files there. It does not keep a shadow copy of your app to compile in secret.

Nothing in this list is your App Store .p8, Play JSON, or keystore. Those stay in CapWrap’s vault. CI fetches them for one run only. See What happens during a build.

Add Capacitor (wrap)

Typical files on capwrap/add-capacitor:

FilePurpose
package.jsonAdds @capacitor/core, CLI, ios / android packages
capacitor.config.tsApp ID, app name, web folder
.gitignoreIgnores Pods, Gradle build, copied web assets
resources/README.mdPlaceholder for icon and splash
scripts/capwrap-add-native.shHelper to run npx cap add
.github/workflows/capwrap-capacitor-init.ymlOn that wrap branch, CI runs npx cap add ios/android and commits ios/ and android/

The init workflow runs on the wrap branch, not on every later push. After merge, those native folders should live on your default branch.

Lockfile (package-lock.json / pnpm-lock.yaml) is not updated in the wrap PR. Install in Lovable or locally after merge.

Native store pipeline

Installed from Settings → Pipelines (branch capwrap/native-pipeline unless you commit directly):

FilePurpose
.github/workflows/capwrap-native.ymlThe job CapWrap starts when you ship
.capwrap/FastfileFastlane lanes: TestFlight + Play Internal
.capwrap/fetch-secrets.shDownloads store keys + app env for this run
.capwrap/build-web.shBuilds the website into a folder with index.html
.capwrap/report.shTells CapWrap which step succeeded or failed
.capwrap/keep-native.shPacks ios/ and android/ between jobs
.capwrap/install-js.shInstalls npm/pnpm/yarn/bun deps (needed on the Android/iOS jobs so Gradle/CocoaPods can see Capacitor)
.capwrap/run-fastlane.shRuns Fastlane
.capwrap/bump-android-version.pyIncrements Android versionCode
.capwrap/apply-android-signing.pyPoints Gradle at the CapWrap upload keystore
Other .capwrap/* helpersWeb-asset and signing glue

You can rename the workflow file in Settings; CapWrap will dispatch whatever name you saved.

Preview workflow (optional)

If .github/workflows/capwrap-preview.yml exists, GitHub Actions builds the QR preview. If it is missing, CapWrap’s own servers clone that SHA and run the web build. Either way, the preview is a website, not a TestFlight build.

What is not added

  • Your production .env values (vault only)
  • Apple / Google API keys
  • An OTA / Capgo workflow (not installed by CapWrap today)
  • Store listing screenshots

If you hate a PR

Close it on GitHub. Re-run Add Capacitor or Install pipeline later. Removing CapWrap from the dashboard does not revert Git commits.