Description
We’ve improved our Xcode compilation cache integration to ensure you never miss an important build message, even when using log formatters like Fastlane + xcbeautify.
Highlights:
- Never Miss an Error: Some customers using Fastlane and xcbeautify found that test errors or other messages could be hidden due to aggressive log formatting. Now, you’ll always have access to the full raw output.
- Raw Logs Stored Automatically: The Xcode compilation cache now stores the complete unfiltered
xcodebuildlog for each wrapper call in the standard Bitrise deploy directory, under the patternxcelerate-{invocation_id}.log. - Includes Wrapper Details: These log files contain both detailed cache wrapper information (like invocation ID, run stats, and cache config) and the complete underlying build output.
- Simple Access Post-Build: Make sure to add a
Deploy to Bitrise.iostep at the end of your workflow to ensure these logs are uploaded and easily accessible from your build’s Artifacts tab. - How It Works: The Bitrise wrapper streams
xcodebuildoutput both to the console (for live feedback and log formatting) and to these persistent log files. Read more in our deep dive blog post.
Bottom line: With this update, you’re always covered. If a log formatter obfuscates part of your xcodebuild output, you can now find every message and error in the raw log file deployed with your build.