Should we release 0.67.4?

[ShikaSD]

RELEASED - please refer to #18 for 0.67.5

---

Current Release: 0.67.3

Conversations on this thread are limited:

• major release issues
• qualified cherry-pick requests of commits on main that did not make the previous patch version.

Please include a link to the specific commit on main to be cherry-picked, for example: facebook/react-native@bd2b7d6

In other words, if you cannot point to a particular commit on main, then your request likely belongs as a new issue.
If the issue is a major release issue, please reference the issue here.

---

List of qualified picks

1. facebook/react-native@8d50bf11335

Local commits to backport to main

[mikehardy]

Copied from #13 (comment)

Just saw this in react-native weekly digest - seemed like this affects back to the 0.66 tree and was finally merged, but recently enough it is not on the pick list here? facebook/react-native@8d50bf11335 - fixes a regression in Switch behavior. I'll post similar comments on 0.67 / 0.66 release planning threads but @d4vidi / @asafkorem / @jonathanmos might do well to keep eyes on it 👀 - my comments are intended to bridge people into this maybe-pick-it conversation but I am likely not most aware person for this change

[cortinico]

This is offtopic:

In other words, if you cannot point to a particular commit on main, then your request likely belongs as a new issue.
If the issue is a major release issue, please reference the issue here.

If the issue gets fixed, you can ask for it to be backported to a potential 0.67.4. But that's not the case at this stage.

[xzilja]

Update causes following build errors on ios (Updated from 0.67.3). Expanding on these errors doesn't give any extra info I'm afraid. I also tried

• Removing Podfile.lock, Pods and .xcworkspace
• Removing DerrivedData folder
• Re-installing pods and re-generating xcworkspace
• Cleaning build

Error still persists. Downgrading back to 0.67.3 solves it.

This happens in latest XCode version / M1 Mac

[mikehardy]

Got my hands on the M1. Everything worked fine for me, Xcode 13.3 / macOS 12.3, ios debug +hermes +flipper - didn't check release but that wasn't specified. works for me?

[xzilja]

@mikehardy Alright, thank you for checking this out. Sounds like the issue is specific to me (eh..) Will have to investigate further. Wonder if following things can have an effect on this:

1. I recently updated to latest cocoapods version (1.11.3)
2. My nodejs / cocoapods are installed through homebrew

I'll try your suggested approach of running that command manually from terminal as well 👌 hopefully that gives more concrete error.

[xzilja]

Well after a lot of fighting, my issue was resolved by completely deleting the repo and re-pulling it again from github. I was then able to update. Still no clue what was the issue last time though.

[leotm]

great stuff ^ git -fdx helped me recently too and upgrading to new arch a ton

roughly equivalent to delete -> re-clone i think/hope

[leotm]

oh and mb react-native-clean-project as well ^
@mikehardy noticed you helping there

and everyone else in troubleshooting guide / various other projects

happy to sponsor you guys (when paperwork lands for my next role 🤞)

p.s. what we've learnt here and past is a good night's sleep always seems to be the solution