Road to v0.64 Discussion #214
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Awesome work on this! I'm really excited for Hermes running smoothly on iOS devices. ResolvedSo far, I've noticed two critical issues, and a minor inconvinience:[Critical] AppStore double-checking the min iOS version on 64-bit archivesThe Hermes framework, which gets bundled into your project when you enable hermes on iOS, only supports 64 bit architectures. As per Apple, "Apps that only support 64-bit devices must specify a deployment target of 8.0 or later.". The Hermes framework does not specify the Fastlane logsManually setting I've created an issue for this at facebook/hermes#420 [Critical] Could not get BatchedBridge crash in ReleaseEDIT: That seems to be resolved since I made a fix for reanimated. See my PR here: software-mansion/react-native-reanimated#1469
Debug: ConsoleIn debug builds, everything runs fine and stable on Hermes. I noticed that any |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The thread you linked referenced multiple paths: 1/ I've ran I've also ran pod cache clean --all, which should've removed 2/. ========== On a different note, two of my teammates had no issues building 0.64-rc4, so we tried to push ahead without me. However, we started running into Archive issues. |
"should've" -> did you verify? |
No, I didn't verify at the time. However, I ran and checked just now and |
|
i see |
|
@pvinis, I found it for you. It was removed in facebook/react-native#29792 (I used some FB internal search tools to find it) |
|
Thanks for finding it! Here we go: facebook/react-native#31128 I think this should be merged for the 0.64 release, so we don't end up with a release with weird line endings 😬. |
|
I took another pass at recent comments here. To sum up, I think we have two additional cherry-picks before stable:
Changelog is in progress - https://github.com/react-native-community/releases/pull/220/files I will keep you updated as we complete the above. |
|
@grabbou one more cherry-pick: facebook/react-native#30978 |
|
And maybe this one facebook/react-native#31134 |
|
Everything cherry-picked. No more cherry-picks - everything else will have to wait for a patch release. We're wrapping it up now. |
|
Are we leaving the gitattr out? 🤔 |
Apparently not: facebook/react-native@728d55a |
|
Closing as new release is under way. Let's continue in a follow up issue dedicated to 0.64.0 and upcoming 0.64.1. |
|
Closing as new release is under way. Let's continue in a follow up issue dedicated to 0.64.0 and upcoming 0.64.1. |
|
Any instruction for Update 1: Update 2: |
|
after "npx react-native init AwesomeProject" can't lunch app on ios. through script: through xcode: this is a clean project mac m1 |
|
@N1colasVega you could try this: react-native-community/upgrade-support#138 |



Current latest release: v0.64.0-rc.4
Highlighted Changes
profile-hermesCLI command for converting Hermes tracing profile to Chrome formatPlease see the changelog PR for more details.
Work Required
shelljshas been moved from the rootpackage.jsonintorepo-config/package.json(facebook/react-native@f3930a9), causingpublish-npm.jsscript to fail. I have temporarily installed that package on the CircleCI, but would love additional background on the original commit and whether we can safely move it back to the root. fix: release branches miss workspace dependencies facebook/react-native#30472Already resolved
hermes-enginepod has no version constraints specified, which should probably happen in theReact-Core.podspecfile and lock it with similar version constraints as the one applied to the Android version inpackage.json. Fixed by fix: pin hermes-engine to 0.7.x facebook/react-native#30432react-native-codegenpackage have not been installed. See output here. In progress PR here Integrate Native Module codegen into Xcode build pipeline facebook/react-native#30449file://protocol to resolve that [@grabbou] (added note to changelog, this is expected)pod installoutside ofiosfolder will fail fix(iOS):pod installfails outsideiosfolder facebook/react-native#30469 (temporary solution, will be fixed by Integrate Native Module codegen into Xcode build pipeline facebook/react-native#30449) - cherry picked facebook/react-native@c901c1f, facebook/react-native@5eee2f2 and facebook/react-native@b61aaa1 for the record.Submitting Hermes enabled application to AppStore will fail validation Invalid MinimumOSVersion. Apps that only support 64-bit devices must specify a deployment target of 8.0 or later. MinimumOSVersion in '[My App].app/Frameworks/hermes.framework' is ''." facebook/hermes#420This isn't a release blocker; this issue is triggered when somebody specifies a higher deployment target than the default and can be solved by the user as shown here.i386from valid architectures when building with Hermes on iOS facebook/react-native#30592Hopeful Dates
We can never commit to the dates involved in a release as many things are out of our control. However, we are thinking about these rough dates for this release.
The text was updated successfully, but these errors were encountered: