Skip to content

Broken build option --i-cloud-container-environment #5034

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
jzgoda opened this issue Sep 25, 2019 · 0 comments · Fixed by #5035
Closed

Broken build option --i-cloud-container-environment #5034

jzgoda opened this issue Sep 25, 2019 · 0 comments · Fixed by #5035
Milestone

Comments

@jzgoda
Copy link
Contributor

jzgoda commented Sep 25, 2019

Environment

  • CLI: 6.2.0

Describe the bug
The --i-cloud-container-environment build option was removed from the plist generation, handled by the ExportOptionsPlistService.createDevelopmentExportOptionsPlist method.

To Reproduce
The command:

tns build ios --release --for-device --i-cloud-container-environment Production

Will produce the following error:

error: exportArchive: exportOptionsPlist error for key 'iCloudContainerEnvironment': expected one of {Development, Production}, but no value was provided

Error Domain=IDEFoundationErrorDomain Code=1 "exportOptionsPlist error for key 'iCloudContainerEnvironment': expected one of {Development, Production}, but no value was provided" UserInfo={NSLocalizedDescription=exportOptionsPlist error for key 'iCloudContainerEnvironment': expected one of {Development, Production}, but no value was provided}

** EXPORT FAILED **

Command xcodebuild failed with exit code 70

Expected behavior

A result like:

Exported app to: app/platforms/ios/build/Release-iphoneos
** EXPORT SUCCEEDED **

Project successfully built.
The build result is located at: app/platforms/ios/build/Release-iphoneos/app.ipa

Additional context
This was a feature that I had added (#4526), I will be supplying a PR to fix it.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants