When a build or a connection fails

Before your next build

Before a build starts, we check what it will use. Anything that would make it fail shows on Builds & downloads under Before your next build, and Fix it opens the right step of App setup. A problem stops the build until it's fixed. Lines marked Good to know don't stop it.

• Your icon: there's no icon, it can't be read, or it isn't a 1024 × 1024 PNG without transparency. Upload a new one on the Branding step.
• Your Firebase files: the file for Android or iPhone doesn't match your app's package name or bundle ID. Upload the right google-services.json or GoogleService-Info.plist on the Publishing step.
• Your App Store Connect key: the key ID, the issuer ID or the key file is wrong (it must be the .p8 file App Store Connect gives). Add it again on the Publishing step.
• Your signing keys: your iPhone distribution certificate (.p12) or your Android upload key (keystore) can't be read. Upload it again on the Publishing step.
• Good to know: without Firebase files, notifications won't reach phones. Without an App Store Connect key, the iPhone app can't be sent to App Store Connect.

When a build doesn't finish

The build shows Didn't finish, and nothing from it is published. You get an email and a notification in Yallapp Business, and our team is told. The page says why in plain words, with Fix it when there's a page to fix it on. What the build printed shows the end of the build's output, without your keys and passwords.

Once you've fixed the cause, choose Try again. It starts the build again with the same app version, since nothing was published. When the page has no explanation, it says which part failed, for example "The Android app couldn't be built.", and our team looks into it.

What each explanation means

• The build couldn't use your app's icon: upload a 1024 × 1024 PNG without transparency on the Branding step.
• Your google-services.json is for another Android package name: download it again from Firebase for your app's package name and upload it on the Publishing step.
• Your GoogleService-Info.plist is for another bundle ID: download it again from Firebase for your app's bundle ID and upload it on the Publishing step.
• The Android upload key couldn't be opened: its password doesn't match. Upload the keystore with its passwords again on the Publishing step.
• The iPhone app couldn't be signed: check that the bundle ID exists in your Apple Developer account and that your App Store Connect key has the App Manager role.
• Apple didn't accept your App Store Connect key: create a new key with the App Manager role in App Store Connect › Users and Access › Integrations, and add it on the Publishing step.
• Apple is waiting for you to accept an updated agreement: accept it in App Store Connect › Business, or on developer.apple.com › Account.
• The store already has this version: start the build again with a higher app version.
• Google Play refused the upload: your service account can't release this app. In Play Console › Users and permissions, give it the Release apps permission for your app.
• Google Play doesn't have your app yet: create it in Play Console with your app's package name and upload the first version by hand (the App Bundle on Builds & downloads). After that, uploads are automatic.
• Our build machine had a problem: it wasn't your app. Start the build again; if it happens again, our team will look.

A store problem can also show on a build that is Ready: your files were made, but the upload to a store didn't work. Fix the cause, then start a new build.

A build that stopped

A build usually takes 15 to 45 minutes. If it waits to start for more than a day, or reports nothing for six hours while building, the page says it's taking much longer than usual and has probably stopped. Our team is told. Choose Try again to start it again: the stopped build is closed, and nothing from it is published.

When a connection fails

Your website or platform, your payment keys and your notification keys are checked every day. When one fails, you see a notice on your Overview, a notification in Yallapp Business and an email. Open Integrations, see what failed, fix it and choose Test. See Integrations. If your app uses your own API and it failed its last check, Builds & downloads also says so, with a link to check it. If people don't get their sign-in codes, see Sign-in codes don't arrive.

When a store turns your app down

Before you send your app for review, look at Ready to submit? on the Publishing page: see Ready to submit. If a store turns your app down anyway, see If the store rejects your app.