- 16 Jun 2022
- 2 Minutes to read
- Updated on 16 Jun 2022
- 2 Minutes to read
Build configuration settings
To build iOS apps, you need to enrol in the Apple Developer Program.
The Apple Developer portal at https://developer.apple.com/account will then let you generate and configure many of the required assets, including:
- iOS Distribution certificate (.p12)
- Bundle identifier
- Provisioning profile (.mobileprovision)
The required distribution certificate is a P12 file, which can be made in your Keychain by selecting to export your Apple distribution certificate (.cer) and its private key. See here for step-by-step instructions.
Make sure you generate a iOS Distribution (App Store and Ad Hoc) type certificate, required to make builds with Build Service.
Note that you must set a P12 password. A P12 file without a password will not work with Build Service
Distribution certificate password
The password set when the distribution certificate P12 file was created.
This is the name for your app shown under the app icon in the device home screen, as well as in settings and other places.
The unique bundle identifier for your app. It will be in the reverse domain format (e.g.
com.appgyver.myapp.production and must match the bundle identifier registered in the Apple Developer portal.
Provisioning profile for App Store
An App Store provisioning profile (.mobileprovision) generated for the app in Apple Developer portal. Must match the registered bundle identifier and the iOS distribution certificate.
External iOS/Web Apps can use this URL scheme to integrate with your app and provide a more seamless experience for the user. For example, a user can launch your app by clicking a link directed at the URL scheme (in the same manner as clicking an iTunes link launches the iTunes app and plays the song specified in the link).
Define the URL scheme via a the following universal format:
On the Build Settings page you can choose a runtime version and set the version properties for the build.
Internal version code for the current build. e.g.
Semantic version number for the current build, e.g.
Image assets and permissions
Check out this guide.
There's an outstanding issue where an iOS binary built with the AppGyver Build Service fails to process in App Store Connect if it's uploaded via the Transporter app when Xcode is not installed.
Installing Xcode resolves the issue and allows the Transporter app to be used normally.
After the build is done processing, you can use Apple's TestFlight service to distribute it to members of your Apple Developer organization.
If you submit your app to Apple's Beta Review, you can also generate a public link to join your app's beta testing.
Once you're happy with your app, you can send it to Apple for actual review. After getting accepted, your app will be available on the public App Store.
Finally, you can use Apple Business Manager to limit your app's access to just your organization, or to specific users via download codes.