Diagnosing your upload failure

When Waldo rejects your upload

During onboarding, you are presented with a screen inviting you to upload a buildbuild - A build is a specific instance of an application created at a specific point in time. A build can be an IPA (iOS), a (zipped) “.app” bundle (iOS), or an APK (Android). Ideally, a build should be uniquely identified by version number (and build number on iOS), but Waldo does not require it. of your app for the first time.

When you attempt to upload your first build to Waldo, Waldo performs a series of validation checks to ensure that your build is correctly constructed. It can’t catch everything in advance (yet), but it does detect many common mistakes.

Most importantly, Waldo expects that your build is made for Simulators.

Once you get past the initial validation, Waldo performs some deeper validation checks.

We currently support builds made on x86_64 architecture only (for now).

Your build must be compatible with our current default device. In this example, it is iOS 13.3.0.

When an error happens, the instruction modal will open with an error banner to help you understand what went wrong.

We also created a series of step-by-step videos to help you build your app.


The following error occurs in the rare case where there is not enough space available in your application’s binary header for Waldo to prepare for running on a (simulator) device. We suggest adding the following line to your Xcode build settings:

OTHER_LDFLAGS = -headerpad_max_install_names

Watch instruction video

Creating your build again in Xcode with this setting enabled nearly always alleviates the problem.

Once you have corrected all identified problems with your build, you can upload it to Waldo successfully, and then create your first testtest - A test is a flow combined with a set of assertions that define the criteria for acceptance.!