How I Downgraded Xcode
๐
Before getting started ๐
While developing a React Native and Expo app, unexpected build errors began immediately after I updated Xcode to 16.3.
The console repeatedly reported template errors involving
std::char_traits<unsigned char>, and compilation stopped in some Pods.
To resolve the problem quickly, I decided to downgrade
Xcode to 16.2.
This article describes what happened and walks through a safe downgrade step by step.Errors after the Xcode 16.3 update ๐
After the update, the build stopped with the following error.
static_assert(is_same<_CharT, typename traits_type::char_type>::value,
^ implicit instantiation of undefined template 'std::char_traits<unsigned char>'
The error occurred in the C++ standard library around
string_view and appeared to involve compatibility with React Native Pods such as RCT-Folly and React-perflogger.In short,
the new Xcode version was incompatible with some existing C++ native code
.
Because I do not work directly with C++ code in this Expo project, returning to a stable previous version was faster than addressing the underlying issue.Downgrading Xcode from 16.3 to 16.2 ๐
The process has four main steps.
1. Removing or renaming Xcode 16.3 ๐
Only one application named
Xcode.app can occupy the location, so delete the existing version or rename it.
To delete it:
sudo rm -rf /Applications/Xcode.app
Alternatively, rename it and keep it:
sudo mv /Applications/Xcode.app /Applications/Xcode-16.3.app
This provides a backup if you want to use 16.3 again later.
2. Downloading Xcode 16.2 ๐
Download Xcode 16.2 from the following page.
๐ Apple Developer Downloadsโ
- Sign in with your Apple ID.
- Search for Xcode 16.2 and download the
.xipfile.
3. Installing Xcode 16.2 ๐
Double-click the downloaded
.xip file to extract it, then move the application to /Applications.
You can also drag and drop it there.sudo mv ~/Downloads/Xcode.app /Applications/
4. Activating Xcode 16.2 ๐
Finally, use
xcode-select to specify which Xcode installation the system should use.sudo xcode-select -s /Applications/Xcode.app
Verify the active version with the following command.
xcodebuild -version
Expected output:
Xcode 16.2
Build version 16Cxxx
Building the project again should now work without the error.
Conclusion ๐
This experience reminded me that
the latest version is not always the most stable
.
For frameworks tied to native components, such as React Native, pay attention to compatibility with Xcode and Android Studio versions.
Before major updates, I plan to check GitHub issues and Expo release notes.
