Replies: 42 comments 211 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
Sharing this from the React Native issue tracker: We might have to look closely into this and work on a fix for it. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
My apologies in advance if this is not the correct place for this but I encountered the following while upgrading to 0.69.0-rc.1. I don't mind moving this or parts of this to the correct location if needed. OS: Void Linux Not sure how useful this is but I had issues building Hermes after manually upgrading from 0.68.1 to 0.69.0-rc.1 by following https://react-native-community.github.io/upgrade-helper/?from=0.68.1&to=0.69.0-rc.0. As a side note I am also using the 0.68.1 TypeScript template. 1. The first issue was related to not enabling Hermes but it builds when the new architecture is enabled anyway. Not a huge problem as the docs above (reactwg/react-native-new-architecture#4) explain that Hermes is built with RN 0.69 and that ensures the versions are compatible. Maybe a note in the docs that this overrides the enableHermes config would prevent confusion since this is new. 2. The second issue that caused the first to be more of a confusion was that Hermes would fail to build and it was not immediately clear why as I could not find anyone else with this issue.
To fix this I installed icu-devel using I figured that much out by looking at https://github.com/facebook/hermes/blob/f11379f0564fd2b93a6024debffccd5eebce547e/CMakeLists.txt#L465 and seeing that it was expecting a Maybe another note could be added to the docs for Linux users that encounter this issue as building Hermes with React Native is new to 0.69. Or maybe this is a one off issue just for me. I saw that ICU is required for building Hermes but I did not see this issue in the Hermes repository. Should the Hermes build process contain ICU or download it for systems that don't already have ICU? 3. The last issue actually occurred prior to the Hermes issues but I saved it for last as it may not be related to this discussion. I kept getting:
I read on a related stack overflow question that this can be caused by having insufficient privileges but running again with sudo did not fix the issue. To fix this issue I installed mkdirp and then the Hermes issues began. I hope this is helpful. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
When upgrading from 0.68.1 to 0.69.0-rc.0 got:
Although the lib is apparently fine i removed it and then the same occurs but this time saying that the firebase lib could not be found in root project... |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
question: how do you setup jest with react-native 0.69? it works fine with 0.68.2. i got an error when i try to run jest unit test:
i do have this is my jest.config.js:
|
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
hey. i upgrade react-native from 0.69.0-rc.3 to 0.69.0-rc.5. i got an error with the start command:
i use metro version 0.71.0:
any idea why? |
Beta Was this translation helpful? Give feedback.
-
iOS with new arch looking good, some Android results below following up earlier discussion
MacBook Pro (13-inch, M1, 2020), JDK 18 aarch64 java.lang.OutOfMemoryErrorError reporting crash
java.lang.OutOfMemoryError: Failed to allocate a 320848968 byte allocation with 4742061 free bytes and 187MB until OOM, target footprint 9582429, growth limit 201326592
at java.util.Arrays.copyOf(Arrays.java:3257)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuilder.append(StringBuilder.java:137)
at java.lang.Throwable.toString(Throwable.java:493)
at java.lang.String.valueOf(String.java:2924)
at java.io.PrintWriter.println(PrintWriter.java:754)
at java.lang.Throwable$WrappedPrintWriter.println(Throwable.java:778)
at java.lang.Throwable.printStackTrace(Throwable.java:667)
at java.lang.Throwable.printStackTrace(Throwable.java:735)
at android.app.ApplicationErrorReport$CrashInfo.<init>(ApplicationErrorReport.java:354)
at android.app.ApplicationErrorReport$ParcelableCrashInfo.<init>(ApplicationErrorReport.java:484)
at com.android.internal.os.RuntimeInit$KillApplicationHandler.uncaughtException(RuntimeInit.java:157)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1073)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1068)
at java.lang.Thread.dispatchUncaughtException(Thread.java:2200)asdf |
Beta Was this translation helpful? Give feedback.
-
Unfortunatly, we have to DISABLE Hermes since a long time due to usage of REGEX named capture groups. Will it be available without Hermes? Thanks |
Beta Was this translation helpful? Give feedback.
-
Just to report that I can successfully build and run (with and without hermes ) the default template using npx react-native init RN069RC6 --version 0.69.0-rc.6 on a 2020 M1 Air 16GB (reinstalled OS from scratch, no Rosetta, latest Xcode and Android Studio) using node, watchman, yarn, cocoapods, ruby, zulu11 from homebrew (and coreutils to remove messages about missing realpath). Everything went fast and clean. Thanks to everybody for the great job. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
we would like to have these two commits in 0.69-stable for expo + swift integration when people get a chance. thanks! |
Beta Was this translation helpful? Give feedback.
-
We would like to have facebook/react-native#34004 merged in 0.69. |
Beta Was this translation helpful? Give feedback.
-
Undefined symbols for architecture x86_64:
"folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::deferredReaders", referenced from:
void folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::applyDeferredReaders<folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::WaitForever>(unsigned int&, folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::WaitForever&) in AppDelegate.o
void folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::applyDeferredReaders<folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::WaitForever>(unsigned int&, folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::WaitForever&, unsigned int) in AppDelegate.o
"folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::unlock()", referenced from:
std::__1::unique_lock<folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false> >::~unique_lock() in AppDelegate.o
"folly::SharedMutexImpl<false, void, std::__1::atomic, false, false, false>::~SharedMutexImpl()", referenced from:
std::__1::__shared_ptr_emplace<facebook::react::ContextContainer const, std::__1::allocator<facebook::react::ContextContainer const> >::__on_zero_shared() in AppDelegate.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
cause seems related to Flipper, remembering similar last yr 😅 defaults atm to 0.125.0 # ios/Podfile
# ...
- use_flipper!()
+ # use_flipper!()
# ...
now building/running fine
|
Beta Was this translation helpful? Give feedback.
-
Hello guys. I tried to run the project on the latest version and I get crashed right away Steps to reproduce
NoteOS: Simple errorDetailed loghttps://gradle.com/s/xce3fbozvtzeg react-native info
|
Beta Was this translation helpful? Give feedback.
-
Does anyone who use Mac M1 can help? As i notice the 0.69 is almost ready for launch but unfortunately we are not having success building it. Upgrading from 0.68.2 to 0.69.0-rc.6 causes the Android Build to crash when opening the App. Error message: Missing Realm constructor. Did you run "pod install"? + Info
Important Libs build.gradle
npx info
|
Beta Was this translation helpful? Give feedback.
-
How to link assets like font files to the project in RN 0.69? Now I am getting following error
Here is my react-native.config.js file
|
Beta Was this translation helpful? Give feedback.
-
I am trying to update my app to 0.69-rc6, and hit this issue: facebook/react-native#33976 Also FYI |
Beta Was this translation helpful? Give feedback.
-
Looks something with Yoga in 0.69.0 |
Beta Was this translation helpful? Give feedback.
-
2022-06-22 Update
React Native version 0.69.0 has been released (0.69.0-rc.6 has been promoted to stable) 🎉
Conversation about the patch version of 0.69.1 is happening here
The branch cut has happened.
Notice
Highlighted Changes in this release
A full detail of the release changes is available in the Changelog PR
React Native 0.69.0 will contain some significant changes that we would love to ask release testers to try.
Hermes Distribution Model
React Native 0.69.0 contains changes to how Hermes is distributed to you. The change will improve the general stability of the Engine and will make sure you're a consuming a engine that is fully compatible with a specific React Native version. This change is described here in detail.
How to test Enable Hermes following the usual instructions here https://reactnative.dev/docs/next/hermes and report any issue you're facing for Hermes in this discussion.
React 18 & Concurrent React
React Native 0.69.0 will be the first version of React Native to ship with React 18.
Users on the New Architecture, will be able to use the Concurrent React features.
By default, we're enabling Concurrent React features for users on the New Architecture.
More documentation on how to use Concurrent React within React Native can be found here.
How to test Create a React Native app enabling the New Architecture. Toggle the
concurrentRootEnabled
method and report any issue you're facing to this discussion on the New Architecture Working Group.New Architecture
We're continuing the rollout of the New Architecture, started in React Native 0.68.
Specific issues that are related to the New Architecture should be reported inside the New Architecture Working group. If you're not a member, you can request an invite here.
Release Process
Checklist
react-native-website
to ship new versionRetrospective Topics
Release Status
Tracking 0.69.0-rc.7
Picks for 0.69.0-rc.7
Tracking 0.69.0-rc.6
Picks for 0.69.0-rc.6
Tracking 0.69.0-rc.5
Picks for 0.69.0-rc.5
Tracking 0.69.0-rc.4
Picks for 0.69.0-rc.4
Tracking 0.69.0-rc.3
Picks for 0.69.0-rc.3
Tracking 0.69.0-rc.2
Picks for 0.69.0-rc.2
Hermes:
Tracking 0.69.0-rc.1
Blocking issues for releasing 0.69.0-rc.1
Picks for 0.69.0-rc.1
Beta Was this translation helpful? Give feedback.
All reactions