Sorry but there is no raw-xcodebuild-log generated for the failed build.
@jaelim no problem, please send us the build URL via email / the onsite chat or create a report at #issues:build-issues and we’ll check it ASAP! 
Just to highlight this again, generating the mapping in Xcode works as a “workaround” :
That’s exactly what Xcode does when you archive on your Mac, and what the Xcode Archive step tries to generate (the signing mapping config).
You mean Automatically manage signing option is still not available in Bitrise?
@trick14 it is available, and works in most projects.
If it does not work in your project please create a #issues:build-issues report (with the build url), and in the meantime while we’re working on fixing it for your project too, either use the linked workaround (Xcode 9 GM - Failed to create target code sign properties mapping, error) or send us a pull request to the step with a fix (all steps are open source).
Hi,
sorry for the issues with the Xcode Archive & Export for iOS step and thanks for all the reports, and lettings us test with your projects.
We released a new version (2.3.3) of Xcode Archive & Export for iOS step.
Changes:
- fixed scheme - application target mapping
- fixed target - provisioning profile mapping
- handle if archive used NON xcode managed profile
- prefer archive team, if multiple code sign groups found
Please also update the Certificate and Profile Installer step to the new version: 1.9.1.
i am still having this issue
@askari01 if you have the issue with the latest version of the Xcode Archive step, then that’s not related to this thread. In that case please create a new #issues:build-issues report at http://discuss.bitrise.io/c/issues/build-issues