corber build builds your JS Framework app with Cordova assets injected, and then executes a Cordova build. Validators are run to ensure there are no known errors.
corber build --platform=ios --environment=production
ios is the default platform.
Deploying to a device or emulator
After building, you will need to deploy to a device or emulator for testing. A build includes creating the iOS/Android application, but not bundle the run command.
corber open will open your project in Xcode or Android Studio. The IDE can then be used for starting emulators, code signing & app store uploads.
Alternatively, you can deploy to a device or emulator using
corber proxy run, like so:
corber proxy run ios --emulator --nobuild # Deploy to iOS simulator corber proxy run android --device --nobuild # Deploy to Android device
To deploy to an iOS device, you must have Provisioning Profiles set up. Usually, Xcode can set up development profiles for you automatically.
By default, corber produces debug builds. You need to add a
--release flag for Cordova release builds, see the cli reference.
corber build --platform=ios --environment=production --release # Release build for iOS corber build --platform=android --environment=production --release # Release build for Android
Obtaining provisioning profile UUID for signing iOS
When signing while building as described here, you can obtain your iOS provisioning profile UUID by downloading it from iTunesConnect and run the following command:
grep -a -A 1 'UUID' /Users/me/Downloads/myapp_dev.mobileprovision
Cordova Assets & plugins will only be injected to
corber build/serve tasks. Your standard builds will remain unaffected, and will have no additional assets injected.