Closed connorpmullins closed 2 weeks ago
@github-actions bot - I did specify my upgrading version!
FIXED!
I increased the version diff in the React Native Upgrade helper from 0.73.6 -> 0.74.2
to 0.70.13 -> 0.74.2
in an attempt to broaden my search of what could have gone wrong.
I saw that CLANG_CXX_LANGUAGE_STANDARD was modified from "c++17"
to "c++20"
. I must have missed that change during a prior upgrade, but it didn't cause a breaking issue until this release.
Here are some key words so anyone with similar bugs can find this issue: fnv1a, hash_combine, RawProps, too many errors
Environment
System: OS: macOS 14.1.2 CPU: (10) arm64 Apple M1 Pro Memory: 78.89 MB / 32.00 GB Shell: version: "5.9" path: /bin/zsh Binaries: Node: version: 18.15.0 path: ~/.nvm/versions/node/v18.15.0/bin/node Yarn: version: 1.22.21 path: ~/.nvm/versions/node/v18.15.0/bin/yarn npm: version: 9.5.0 path: ~/.nvm/versions/node/v18.15.0/bin/npm Watchman: version: 2023.12.04.00 path: /opt/homebrew/bin/watchman Managers: CocoaPods: version: 1.14.3 path: /Users/connormullins/.rvm/gems/ruby-2.7.5/bin/pod SDKs: iOS SDK: Platforms:
Things I’ve done to figure out my issue
Upgrading version
0.74.2
Description
Disclaimer I may be un-helpable. I realize it's entirely unlikely that there's a significant bug with a stable version of react native that only I've encountered - so I probably have some weird configuration issue. I don't know where else to go with this, however.
I am currently seeing the below issue:
Here is my Podfile - the commented-out code is what I've removed during the upgrade and debugging process.
And since the error references my AppDelegate.mm file, I'll include it here:
Additional (potentially) helpful info: This project is using Expo's bare workflow and there are artifacts from Expo's bare workflow upgrade docs throughout my ios project.
I'm sure this is not a surprise to anyone, but my largest continuing struggle with react-native upgrades is managing the difference in native configuration suggestions between react-native, expo, and the various packages we depend on.
Reproducible demo
I think that if I start a clean project and upgrade, this issue will not exist. I think if I managed to re-create the issue in a new project, then I would also know how to fix it for myself. I'm asking for help, I don't think I'm reporting a bug.