Xcode Archive & Export for iOS v4.0.3

Display verbose debug logs again. (Fix for missing verbose logs, removing Xcode <9 code by lpusok · Pull Request #259 · bitrise-steplib/steps-xcode-archive · GitHub)

It would have been nice to get an email about these changes before they went live. I normally try to use the latest version of the steps so when you made these changes it broke all my builds due to the moving of the furniture and change of the road signs. I was able to get the latest 4.0.3 working with one of my workflows but it’s still failing for another one and the error makes very little sense to me.

▸ Archive Succeeded
Exporting outputs...
The xcodebuild archive log path is now available in the Environment Variable: BITRISE_XCODEBUILD_ARCHIVE_LOG_PATH (value: /Users/vagrant/deploy/xcodebuild-archive.log)
no archive generated at: /var/folders/g2/xnd8hpjs50v433gfrybz2nxh0000gn/T/xcodeArchive508871090/.xcarchive
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | xcode-archive@4 (exit code: 1)                                | 7.3 min  |
+---+---------------------------------------------------------------+----------+

IMHO I don’t think it has simplified anything for me. I thought this was a fairly stable step to use. It’s really not a good idea to rename stuff and not send out emails to let us know. I had originally posted this under the 4.0 notification but really I don’t want to have to come to the forum for change notifications like this and would like it if Bitrise would send out notifications of changes to major steps in an email and given more time to prepare for these changes.

I do apologize for the issues this caused. Totally understand and have passed this information to the development team. We are trying to determine what the best way to notify users in the future of changes like this. Sending an email is definitely an option and is being considered, but we want to make sure that we don’t overwhelm our users with emails so that they get ignored or sent to spam!

We do understand the issue and we are looking into a better way to do this kind of thing in the future. Until then, please accept our apologies.

Would you mind providing details on what issues the changes caused? It would be very helpful if you could provide the build URL for the failing build and enable support access (under the “Settings” tab).

This would help us better understand in order to avoid such issues in the future.

THANKS!