How signing works in Oore
Understand how Oore separates repository-controlled builds from runner-owned mobile signing.
Oore treats repository execution and signing as different authorities. Android is signed by Gradle during the build command, with the keystore the runner hands it for that command. iOS output is signed afterward by fixed logic owned by the Direct macOS runner, and the runner verifies both.
The signing boundary
Signing files, passwords, and API keys are encrypted by oored at rest. The
backend root key is a 0600 file readable only by its operating-system owner in
the daemon data root, so the database and its matching root key belong to the
same recovery set.
For an active assigned job, the trusted runner parent can retrieve signing material with a separate job-scoped capability, and scrubs managed signing values from the environment of repository child processes. iOS signing files, passwords, and the signing capability are never repository build inputs. The Android keystore and its passwords are readable by the Flutter Android build command while it runs, as Gradle needs them to sign.
The runner may hold signing material in its trusted parent while repository stages run. The supported boundary is what repository child processes receive, not a promise that the parent waits until every repository command has finished before retrieving material.
Android signs in Gradle
An Android signing profile contains a keystore, alias, and passwords. For each
flutter build apk or flutter build appbundle command, the runner writes the
keystore to a private folder outside the checkout and adds the Android Gradle
plugin’s android.injected.signing.* properties to the workspace’s
android/gradle.properties, the same mechanism Android Studio and fastlane
use. Gradle signs every variant it builds with them, over the app’s own
signing config. When the command ends, the runner restores the file and
deletes the keystore copy.
The Verify Android signing step (android-sign) then checks each artifact. One signed with the
profile’s key is kept; anything else is signed again in a private signer
workspace and verified. Local developer signing stays independent: a
repository can keep its own key.properties for developer machines without
committing it. See
Keep local Gradle signing alongside Oore.
iOS adds Apple identity and device rules
iOS signing combines a certificate, provisioning profiles, Team ID, and bundle identifier mappings. Oore supports manually uploaded assets, App Store Connect API synchronization, and a hybrid of those paths.
The Direct runner account must have an active macOS login session. Oore creates temporary job signing state and attempts to restore and remove it after the job. Profiles stay in the private job workspace. This cleanup is defense-in-depth, not hostile-code isolation for repositories already trusted to run as that macOS account.
What this means for you
- Do not pass Oore-managed signing credentials through repository environment variables or Gradle source. Gradle gets the Android keystore without either.
- Treat Android build commands as able to read the Android keystore while they run, and only build repositories you trust with it.
- Keep an independent backup of signing keys and passwords.
- Treat the Direct runner account as sensitive and preferably dedicated and non-admin.
- A successful repository build can still fail later if signing or signature verification fails.
- An iOS install also depends on a matching, unexpired provisioning profile and registered-device eligibility.
Next step
Add Android signing or configure manual iOS signing. Use the environment reference for supported repository inputs.