-
Notifications
You must be signed in to change notification settings - Fork 1
Running on a Physical Device
In addition to issuing the command to send to a connected physical iOS device:
./gradlew ios:launchIOSDevice --info --stacktrace
which is defined in the robovm gradle plugin, we must manage signing and certificates to get our application installed correctly.
There are two ways to do this, the easiest being to let Xcode manage the singing automatically, requiring a minimal setup as described below.
To set up automatic management of certificates and signing for a Quorum RoboVM project with Xcode:
-
First create a blank Xcode project, opening Xcode and going to
File->New->Project->iOS->App -
Once this project has been generated, navigate to the
Signing & Capabilitiespanel of the project -
Ensure that the
Automatically manage signingbox is checked -
Ensure that the bundle identifier in the Xcode project is set to the
app.idused in the robovm.properties fileExample:
app.id=org.quorumlanguage -
Select a
team,provisioning profile, andSigning Certificate. Some of these may be generated and filled in when selecting a team.Note: A good reference on these code signing files and their generation is available here
Once this project has been created, and indexed by Xcode, when running the install on a physical device Xcode is now able to associate the bundle identifier to our app.id, allowing for automatic management of signing and certificates.
Sample screenshots:
| Blank Xcode Project | robovm.properties |
|---|---|
![]() |
![]() |
The signing identity and certificates can also be managed from the build.gradle script located within the iOS project subfolder, where this can be configured as follows for ipa creation:
robovm {
iosSignIdentity = "your signing identity"
iosProvisioningProfile = "your provisioning profile"
iosSkipSigning = false
stdoutFifo = ""
stderrFifo = ""
}

