Specify how the Apple application will be executed.
|Build for Distribution (Local) ||Transfers the XCode project to a Mac and compiles the application using the distribution signature generating an *.ipa file. Next, the file is copied to the KB environment folder.|
|Build IPA (Local) ||Transfers the XCode project to a Mac and compiles the application using the development signature generating an *.ipa file. Next, the file is copied to the KB environment folder.|
|iOS Device (Mac) ||Transfers the XCode project to a Mac, compiles the application and executes it in the physical device connected to the Mac. The Development Team ID property must be set.|
|iTunes Sync (Local) ||Transfers the XCode project to a Mac and compiles the application generating an *.ipa file. Next, it copies it from the Mac to the development PC (note that the Output window of the GeneXus IDE shows the path where it was copied to), and automatically opens iTunes to show the application in the application catalog.|
|Knowledge Base Navigator (Device) ||The application metadata is generated and if a device is specified in the Execution Device property, the application is opened in that device using the KBN (Knowledge Base Navigator). No Mac is needed in this process.|
|Simulator (Mac) ||Transfers the XCode project to a Mac, compiles the application and executes it in the simulator specified in the iOS Simulator property.|
Platforms: Smart Devices(IOS)
An *.ipa file is an iOS application archive file that stores an iOS app.
GeneXus uses the XCode command-line tool package called xcodebuild to generate the application in the Mac environment.
The generated Xcode project is created with the "Automatically manage signing" property enabled. This function only is useful when the application will be executed in a physical device and in order to make it properly work, the following must be considered:
Development Team ID property must be set.
A valid application signing profile and certificate must exist in Xcode or a proper account with the necessary permissions over profiles, app ids and certificate must be configured in Xcode accounts option.
It is highly recommended that the developer stores the build/<MainObjectName>.xcarchive file in every release of the application. This is important if the developer wants to build and install an old version of the application, which may not be available anymore on the App Store or TestFlight.
When building for executing in a device (Build for Distribution, Build IPA, iOS Device or iTunes Sync options), GeneXus may throw an error. You will need to go to the Mac Terminal and manually execute (only the first time) the sshExec command that is failing (it is the command that contains "-allowProvisioningUpdates"). This situation happen because the the ssh session where the command is being executed, is not interactive.
Local building options are unavailable for GeneXus 15 U1, U2, U3, U4. In these cases, refer to HowTo: Create an .ipa file from XCode for creating it manually.
When building In-House applications
you will need to perform the last steps of the application distribution in Xcode. A typical process would be to build the application with any of the availables execution types (excepting the one for KBN) and after that open the project in Xcode and continue the process of Archive and Distribute from there, following the indications from the Apple documentation
This property applies only at design-time.
To apply the corresponding changes when the property value is configured, execute a Build All.