The file that is your app will be referred to as a 'binary' or 'build'. Oomph's app building system allows you to build a tester binary and the binary that you will submit to the App Store.
Once you have uploaded all of the required (and optional) assets and have uploaded existing or renewed certificates, profiles etc. as detailed in these steps, you're ready to create your binary.
Building an app
Navigate to the Build App tab on the left hand side, underneath BUILDS. If you are missing any required files, you will be shown an error message detailing what is still required.
Here you can input the app version (e.g. 1.0.0). If you don't choose one, one will automatically be generated for you by Oomph. Provided everything has already been uploaded correctly, all you will need to do is hit the "Create App Store Build for App Name" button. The system will then go ahead and build your application at the latest released version of Oomph.
Note: If you require your app to be built on a specific version, you will need to contact firstname.lastname@example.org.
A build can take anywhere from about 5 mins to 1 hour to complete, depending on the size of the assets, the type of the app and how busy our server is at the time.
Downloading your app
Once a build is complete, it will be available under the View All tab underneath BUILDS. This tab stores all your previous build, listed from most recent to oldest.
Each build will have its own build number, the time and date that it was created (AEST), the app version, the Oomph magdata (kit) version, the status of the build (success or fail) and the option to download it.
Click on Download Build, and you will download a zip folder that contains the below files (once unzipped). You will receive five files, consisting of your Ad Hoc build (aka tester), the dSYM file, the actual App Store version that you upload to Apple and some log files.
The only files that you will be using are the first file with "TESTER.ipa" at the end of the file name: this is the "Ad Hoc build".
You will also use the third file to upload to Apple: this is the App Store build.
The second file is the the dSYM file. The dSYM is the file used to symbolicate any crash logs that a build may have, and is only really used by our development team in the unlikely event that something is wrong with your app build.
Once you have successfully downloaded your build and have created the app in iTunes Connect, then you are ready to upload your application to Apple.
When a build fails, clicking Download Build will give you an output.log file. This file can be opened with any normal text editor (e.g. TextEdit). It will detail what was outputted to the console while attempting to build the application, and where the error was.
In some cases this file can be easily read and interpreted. Please read here for a list of common errors. If the failures are not listed, or you can't interpret the error, you may need to contact us for further assistance.