Skip to content

can't export ipa while using icloud #4374

New issue

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

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

Already on GitHub? Sign in to your account

Closed
farfromrefug opened this issue Feb 19, 2019 · 5 comments
Closed

can't export ipa while using icloud #4374

farfromrefug opened this issue Feb 19, 2019 · 5 comments
Assignees
Milestone

Comments

@farfromrefug
Copy link
Contributor

On iOS, i am trying to export an ipa (run app on device) which uses icloud documents.
I get this 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}

It seems that the export plist here does not contain the correct value for iCloudContainerEnvironment

@DimitarTachev DimitarTachev self-assigned this Feb 25, 2019
@DimitarTachev
Copy link
Contributor

Hi @farfromrefug,

Thanks for investigating that, I'm marking the issue as a feature request as we both do not provide any value for iCloudContainerEnvironment and we do not support extending this Export Options Plist.

@jzgoda
Copy link
Contributor

jzgoda commented Apr 8, 2019

@farfromrefug or @DimitarTachev, is there a workaround for this issue?

This is the only thing preventing me from upgrading an enterprise app the latest version of {N}.
How else am I supposed to get an .xcarchive if I can't use --forDevice?

Currently, I build with:

tns build ios --bundle --env.uglify --env.aot --release --forDevice

(Then I export my enterprise release with the .xcarchive created from the above command.)

@farfromrefug
Copy link
Contributor Author

@jzgoda you have to manually patch {N} :s could make a hook to do that.
You need to change this to add the correct iCloudContainerEnvironment

@jzgoda
Copy link
Contributor

jzgoda commented Apr 9, 2019

@farfromrefug, thanks for sending me down that path!

After playing around with that code, I was able to build my enterprise .ipa without the additional step of building it from the .xcarchive that was previously generated!

However, forced patching the CLI is not an optimal way of building apps.
This would be SOOO much easier if we could just supply our own exportOptionsPlist, similar to how xcodebuild does.

@DimitarTodorov, does this sound like something that would be allowed?
(I'd be willing to try to implement it.)

@jzgoda
Copy link
Contributor

jzgoda commented Apr 9, 2019

For clarity, I was thinking of something like:

tns build ios --bundle --env.uglify --env.aot --release --for-device --export-options exportOptions.plist

Edit:

Upon further investigation (and use of the --provision option) the only additional parameter I needed was iCloudContainerEnvironment. After looking at how provision and teamId are implemented, it doesn't look like this should be too difficult.

@ghost ghost added the new PR label Apr 10, 2019
@Fatme Fatme added this to the 5.4.0 milestone Apr 11, 2019
@Fatme Fatme self-assigned this Apr 11, 2019
@ghost ghost removed the new PR label Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants