fix(ios): build fmt pod as C++17 to fix Xcode 26.4+ consteval error#314
Merged
mfazekas merged 1 commit intoJul 3, 2026
Merged
Conversation
mfazekas
force-pushed
the
fix/ios-experimental-fmt-consteval
branch
from
b394e29 to
c0a1469
Compare
Interim workaround for the Apple clang 21 consteval error in fmt, matching Expo's recommended fix (expo/expo#44229): define FMT_USE_CONSTEVAL=0 on the fmt pod while keeping C++20. The real fix is upstream in React Native 0.83+.
mfazekas
force-pushed
the
fix/ios-experimental-fmt-consteval
branch
from
c0a1469 to
cbeb8a6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-picks the
fmt-as-C++17 Podfile workaround onto the experimental backend line so its iOS build survives the Xcode 26.4+ (Apple clang 21)constevalerror infmt(via RCT-Folly on RN 0.80.3).Same change as #306 (which targets
main); applies cleanly here and the branch had no prior fmt workaround. Remove once we bump to RN 0.83+ (fix is upstream there).