Common Issues

Build Failure

There may be a bunch of reasons for a build to fail.

Best way to learn the reason is to check the build logs. See Working With Build Logs section for details on this.

Build logs will display everything happened in each workflow step in details and let you examine what went wrong during the build.

If you are unable to determine the exact cause, feel free to get in touch with Appcircle using the in-app messaging for additional support.

Troubleshooting Workflow Steps for Build Failures

Most build failures are related with the following build steps. If you encounter any errors, please remove or edit the following steps and get a build to help isolate the cause of the issue.

  • iOS Sign Errors: If the selected provisioning profile does not match with the selected bundle ID or if the certificate is not valid, you may have an issue in the iOS signing step. In this case, you may try getting an unsigned build

  • Xcode Build for Simulator step: This step is required to use the Preview on Device feature and it requires the app to be built for the x86 architecture. In some projects, there may be dependencies that are not compatible with x86. In this case, please remove this step from the workflow or remove the conflicting dependencies to get a successful build.

  • Android Sign Errors: If you encounter errors while signing your Android app, you can remove this step to get an unsigned build or you can configurethe app signing within your project.

Build Is Taking Too Long

With every build, a brand new virtual machine is started to perform your workflow and build your application.

Some applications may have 3rd party dependencies which need to be installed before the build is performed. With every new build, these dependencies need to be re-installed.

One way to speed up the build time may be to manage your dependencies in your project. This will speed up your builds significantly if your application has excess amount of dependencies to be installed.

If you still think that your build is taking significantly longer than it should, please feel free to get in touch with Appcircle for additional support.

iOS Xcode Scheme Errors

Your iOS application project needs to have a shared scheme in order to be built outside Xcode. Xcode doesn't share schemes by default so you will have to do it manually.

  1. On Xcode, select Product > Scheme > Manage Schemes

  2. Select Shared for your xcproject or xcworkspace

  3. Scheme container needs to be set to the corresponding Xcode project or workspace

  4. Please do not forget to add your .xcscheme file to version control so it will be uploaded to your Git repository

For details on iOS builds please refer to Building iOS Applications‚Äč

Android Keystore Errors

Missing keystore path error on Android builds

You may want to build unsigned Android applications. Most common mistake done with this is Appcircle users usually forget to disable Sign Application step in the workflow.

If you do not select a keystore in the build configuration, you need to disable the Sign Application step or your build will fail.

Keystore was tempered with or password was incorrect

You may get this error message when the provided password doesn't match the keystore file.

If you are using a debug keystore, simply re-generate it. Otherwise, please make sure you have the correct keystore/password combination.

Repository Issues

Please note that currently only Git repositories are supported. Any third party version control repositories need to be transferred to a proper Git repository on either Github or Bitbucket.

How to change your connected GitHub, Bitbucket or GitLab account

You will need to go to your Github, Bitbucket or GitLab account and revoke access to Appcircle and then reconnect your account from Appcircle.