We have released a new version (2.4.11) of Xcode Archive & Export for iOS step.
Changes:
- CloudKit support
We have released a new version (2.4.11) of Xcode Archive & Export for iOS step.
Changes:
@godreikrisztian This version of Xcode Archive & Export for iOS step is broken. It tries to find the project file in project file and obviously failed.
Fix was published - can you try it again with the latest version @snowtema?
Yep, just a moment
Let us know if you’d still have this issue!
Oops, my bad @snowtema - the new version is not accepted just yet: https://github.com/bitrise-io/bitrise-steplib/pull/1624
Will be in a couple of minutes, once the tests pass.
Was just merged, so if you have the step on “always latest” it should now pick up the new version (2.4.12
)
@viktorbenei So, with version option “Always latest” works fine.
So I had this issue with (exit code: 1)
issue with v2.4.11
and v2.4.12
.
Had to revert back to v2.4.10
for archive to work.
with v2.4.11
before the archive worked, I’d get an error saying steplib
missing just before the archive step started.
with v2.4.12
I’d get an error saying missing scheme for the workspace.
I’ll update here with more detailed logs if that is helpful (after I’m done submitting a new version to the app store.)
Hi @viktorbenei,
I am also facing the following bitwise error when exporting the IPA
is there any steps need to follow ? , FYI : in my app used the iCloud features
2018-08-02 00:04:36.356 xcodebuild[4181:19445] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/SoCredit_2018-08-02_00-04-36.354.xcdistributionlogs'.
2018-08-02 00:04:38.238 xcodebuild[4181:19445] [MT] IDEDistribution: Step failed: <IDEDistributionOptionsStep: 0x7fa871998f30>: 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}
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 **
[00:04:38]: Exit status: 70
can you suggest me regarding this error ?
Thank you.
Having issues too. Our builds ran fine yesterday before this step updated and now we have this. Rolling back fixed it.
Hi
We have issue with v2.4.11
Exporting ipa with ExportOptions.plist
No custom export options content provided, generating export options...
export-method specified: app-store
Failed to get target (React) bundle id: key: string("INFOPLIST_FILE") not found in: serialized.Object
+1
Having the same issue.
Same issue:
Exporting ipa with ExportOptions.plist
No custom export options content provided, generating export options…
export-method specified: app-store
e[31;1mFailed to get target (Mogenerator) bundle id: key: string(“INFOPLIST_FILE”) not found in: serialized.Object…
Hi all!
We have released a fix with the version of 2.4.12.
Please change the version to 2.4.12 and try with that.
Sorry for the inconvenience and thanks for reporting!
If you have an issue with the latest version (2.4.12
) please report it via the onsite chat or in #issues:build-issues so that we can check e.g. the related build’s log and fix the issue quickly!
Hi @Nandhakumar have you specified the icloud_container_environment
input?
Hi @MattCheetham, could you please attach a build url of your previous green build and the recent failed with the new version?
Hi @AVKarelin could you please write us on the on-site-chat and send us:
and would need to have a look them to identify the issue.
Hi @bsidoti could you please write us on the on-site-chat and send us:
and would need to have a look them to identify the issue.