# Build Cache for Xcode v0.23.2

**URL:** <https://discuss.bitrise.io/t/build-cache-for-xcode-v0-23-2/26280>\
**Category:** Changelog\
**Tags:** step-update\
**Created:** [September 16, 2026, 10:50am UTC](https://discuss.bitrise.io/t/build-cache-for-xcode-v0-23-2/26280 "2026-09-16T10:50:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [September 16, 2026, 10:50am UTC](https://discuss.bitrise.io/t/build-cache-for-xcode-v0-23-2/26280/1 "2026-09-16T10:50:01Z")

</div>

## What’s Changed

- Bumps the CLI to v3.9.2, which makes `xcodebuild` query actions report the DerivedData the build actually uses.
- `-showBuildSettings` was answered from the default DerivedData while products were emplaced under the managed root, so any consumer resolving a build product via `TARGET_BUILD_DIR` looked in the wrong place. React Native’s `installApp` was the reported case, but the defect applied to any such consumer.
- Query actions are now handed the same DerivedData as the build, gated on the argv actually accepting the flag.

> **[Release 0.23.2 · bitrise-steplib/bitrise-step-activate-build-cache-for-xcode](https://github.com/bitrise-steplib/bitrise-step-activate-build-cache-for-xcode/releases/0.23.2)**
>
> What's Changed
> 
> Bumps the CLI to v3.9.2, which makes xcodebuild query actions report the DerivedData the build actually uses.
> \-showBuildSettings was answered from the default DerivedData while prod...