| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…or device The `-allowProvisioningUpdates` option is passed to `xcodebuild` no matter if building for device or for simulator. According to the documentation of `xcodebuild`: ``` Allow xcodebuild to communicate with the Apple Developer website. For automatically signed targets, xcodebuild will create and update profiles, app IDs, and certificates. For manually signed targets, xcodebuild will download missing or updated provisioning profiles. Requires a developer account to have been added in Xcode's Accounts preference pane. ``` It seems it shouldn't be passed when building for simulator.
|
test cli-smoke |
Sorry, something went wrong.
|
test cli-device |
Sorry, something went wrong.
|
test cli-device |
Sorry, something went wrong.
|
test cli-device |
Sorry, something went wrong.
|
test cli-device |
Sorry, something went wrong.
|
test cli-device |
Sorry, something went wrong.
|
test cli-device |
Sorry, something went wrong.
|
test cli-device |
Sorry, something went wrong.
|
I'm merging the PR as device tests are green http://nsbuild01.telerik.com:8080/build/job/pr-cli-device-osx/97/ |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The -allowProvisioningUpdates option is passed to xcodebuild no matter if building for device or for simulator.
According to the documentation of xcodebuild:
It seems it shouldn't be passed when building for simulator.
PR Checklist
What is the current behavior?
What is the new behavior?
Fixes/Implements/Closes #[Issue Number].