A failed build isn’t the end of the story – the actual reason it failed is usually easy to find, and re-running once it’s fixed only takes opening the wizard again.
Steps
1. Open Workflow Logs
Find the failed build in your builds table and open Workflow Logs from its row menu. This is where the real failure reason lives – the “Failed” status alone won’t tell you why.
2. Check common causes
- Credentials – a signing certificate or keystore that’s missing, expired, or mismatched.
- Configuration – something in your app’s settings (name, package ID, Firebase files) that’s incomplete or invalid.
- Plugin or connection issues – your website connection dropped, or a required WordPress plugin was deactivated mid-build.
3. Fix the underlying issue
Head to the relevant settings page based on what the logs point to – Publishing Setup covers most credential and configuration causes; Website Connection covers connection-related ones.
4. Try again
There’s no one-click retry on a failed build – re-running means opening Trigger Build again with the underlying issue fixed. See Build your app – and submit it to the store.