Troubleshooting & FAQ
Fixes for the things people hit most.
CI job stays "queued" and never runs
Almost always a stale workspace connection, most common after you reinstall or recreate the GitHub App, which changes its installation id. Go to CI runners and press Reconnect. New jobs should then pick up a runner.
If Reconnect doesn't help, check that the App is installed on the specific repository and that the job's runs-on is exactly buildstack-arc, on its own and not inside a list. [self-hosted, buildstack-arc] is the usual cause of a job that waits forever: it asks for a runner answering to both labels, none exists, and nothing reports an error. The older [self-hosted, buildstack-linux] fleet has been retired, so a job still asking for it waits the same way.
"Out of CI minutes"
You've used this month's allowance. New jobs stay queued until the monthly reset, or upgrade your plan. See CI minutes, build quota & plans.
A deploy/CI job's docker push fails
The runner is daemonless: it has BuildKit, not a Docker daemon. Build and push in one step with docker buildx build --push … instead of docker build followed by a separate docker push.
Google Play rejects my upload
- "Version code N has already been used." Every upload needs a versionCode
higher than the last on Play (any track). Set a higher Version code on the build form. See Versioning your app.
- "signed with the wrong key" / wrong SHA-1. The AAB was signed with a key Play
doesn't expect. Sign with your upload key, or enrol in Play App Signing. Check a keystore's cert with keytool -list -v -keystore your.jks and compare the SHA-1 to the one in Play's error. See Android signing & keystores.
- The AAB format is required for Play, not APK (use a Production build).
- A brand-new app needs its first release uploaded manually in the Play Console;
the API can't create the first release. Later releases automate.
I published to Play but testers don't see it
BuildStack uploads to the Internal track as a draft; it isn't live until you finish it: Play Console → Testing → Internal testing → your draft → Review release → Start rollout.
I clicked "Distribute"/"Release" on a build but nothing reached Google Play
That button shares a BuildStack install link with your own testers (via channels); it does not publish to Google Play. To reach the store, build with Publish to Google Play turned on. See Publish to Google Play and Distribute to testers.
I can't install the iOS build on my iPhone
iOS installs over the air, but Apple only allows it on registered devices:
- The iPhone's UDID must be registered in your Apple account, and the build
must be a development / ad-hoc build. Add the device under the Developer portal → Devices, then rebuild so its provisioning profile includes it.
- Open the install link in Safari — in-app browsers can't trigger the install.
- Seeing "Untrusted Developer"? Trust it under **Settings → General → VPN &
Device Management → your developer → Trust**.
My build can't be signed
Check the project's Keystore (Android) or Apple credentials (iOS) are set. Release builds need signing configured; debug builds are signed automatically.
Logs aren't showing for an old run
BuildStack captures each run's logs into its own storage on completion, but very old runs (or ones that never completed) may only have logs on GitHub, which keeps them for a limited time. The log view will tell you when a log is no longer available.
Still stuck?
Email support@mybuildstack.com with your workspace name and, if it's about a specific run or build, its id.