-
Notifications
You must be signed in to change notification settings - Fork 404
Road to v0.65.0 - RC2 phase #235
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.
I'm unable to build my app on iOS using Xcode 12.5 (intel macOS 11.4). It built fine on 0.64.2. I've used
|
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.
I'm experiencing an error on 0.65.0-rc.1 building for iOS
IPHONEOS_DEPLOYMENT_TARGET = 12.3
From the Podfile.lock:
|
@beetlebum Also noticed this error, seems to be related with the updated Flipper-DoubleConvertion pod. Setting back the version to what it was before fixes it for me. use_flipper!("Flipper" => "0.93.0", "Flipper-DoubleConversion" => "1.1.7") I think the problem is because the double conversion version that we use in react native and the one in flipper is different now and clang can’t dedupe de symbols properly anymore. Cc @PeteTheHeat |
thanks so much, I'll give it a go |
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.
Im having a hard time knowing what was cherry picked and what not, so just for clarity as it’s not in the latest RC: These two for DynamicColorIOS
|
We've been testing 0.65rc-2 but have had to go back to 0.64 due to a few blocking issues, that I'm listing here as they might affect other people:
|
facebook/react-native@2f477b1 allows jest 27 to work with react-native. Please can we include this? |
Really hope this hasn't been mentioned here, and I'm sorry if it has been. Just thought it should get fixed for when On a brand-new Output from
```
$ yarn react-native doctor
yarn run v1.22.10
$ /Users/steven/AwesomeProject/node_modules/.bin/react-native doctor
Common
✓ Node.js
✓ yarn
✖ Watchman - Used for watching changes in the filesystem when in development mode [seems not to have any effect on anything, still works]
- Version found: 2021.06.07.00
- Version supported: 4.x
Android
iOS Errors: 2
|
[edited by @mikehardy to add...] merged as facebook/react-native@6caec9d |
@kelset just a note that I edited the actual description way up at the top to re-point the Hermes + iOS + Apple Silicon build |
Hello. I've upgraded to RN 0.65.0-rc.2 and after removing completely the RN Reanimated and all the libraries depending on it, I've managed to build on Android, but when launching, the app crashes (both with and without Hermes). Seems there is something wrong with the MMKV module installing. I don't know if here is the right place to write, but I don't know where else i can ask this question. Hope this is on the topic, helping for releasing. The log in Flipper contains:
And then the backtrace:
|
Hey, we’d like to have the following PR code in the upcoming release: facebook/react-native#31789 It fixes the support for blobs larger than 64 KB on Android (check the issue: facebook/react-native#31774) How can we accomplish it? Apparently it requires to trigger Facebook team to start reviewing it. |
Hello.
At this point, not being able to find other similar issues with this error, I've decided to test a new dummy React-Native project, to see if the issues is in my existing setup. I've followed the instructions presented in the releases page https://github.com/facebook/react-native/releases and the error is still occurring (with and without hermes) inside the newly created project. Is this a known issue? |
@teniii if the error still occurs in a freshly generated project:
Then it's likely that it's something with your existing setup. |
@kelset issue happens with a freshly generated project. |
Understood - looks like we have a x3 confirmation (tenii, a-eid, tido64) of this |
I *think* I experienced this once, because I had either an old version of
node, or an old version of ws package locked in my lockfile / resolutions.
Might be totally unrelated, just sounded familiar.
…On Wed, 14 Jul 2021, 09:16 Lorenzo Sciandra, ***@***.***> wrote:
Understood - looks like we have a x3 confirmation (tenii, a-eid, tido64)
of this metro-hermes-compiler/src/emhermesc error being thrown - so it's
something we'll have to pay attention to when preparing the next RC. We are
still waiting on Hermes for that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#235 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN4NBDAJFVBBWSIUROZX3TTXVBXTANCNFSM46MHDFRQ>
.
|
@mweststrate could be the issue, I'm using |
@kelset Hi! We've managed to successfully merge this blob fix for Android into the master: Can we cherry-pick it to the upcoming 0.65.0 release now? Thanks. |
This comment has been minimized.
This comment has been minimized.
I've checked and I use |
yeah I think @tido64 was on Node14 and saw it happening too, so probably it's not related to the Node version |
@kelset seems like hermes 0.8.1 was released a few days ago https://github.com/facebook/hermes/releases/tag/v0.8.1 , can you update the description? |
@hsavit1 I'm not sure I know what you mean, the top post is already updated to reflect that Hermes 0.8.1 is out. Update on the metro-hermes-compiler issue: we have a PR with a fix that needs to be merged&released: facebook/metro#687 |
Update on the release: I've cherry-picked few commits, passing over to @Titozzz to wrap up the rest. |
facebook/react-native#31872 Has been created |
bump for Metro to cherry pick: facebook/react-native@cfdc4fe |
RC3 is out, moving conversation over here: #238 |
This issue serves to track the status of work to reach 0.65.0.
Current latest: 0.65.0-rc.2
Changelog draft PR: #234
Known issues
Commits (and PRs) to cherry pick
Non-blocking for RC release
Local commits to backport to main
Please limit your comments to reports of issues encountered with the RC and cherry pick suggestions. No ETA currently for when 0.65.0 will be released.
The text was updated successfully, but these errors were encountered: