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 [self-hosted, buildstack-linux].
"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
- The AAB format is required for Play — not APK.
- Signing must match what Play expects. Use the same keystore as your existing
release, or enrol in Play App Signing. See Android signing & keystores.
- A brand-new app sometimes needs its first upload done manually in the Play
Console; later releases automate.
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.