-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeScheduler is only used by TurboModule Manager in >RN0.72 #2461
Merged
tido64
merged 4 commits into
microsoft:main
from
shwanton:@shwanton/fix-turbomodule-adapter
Jun 16, 2023
Merged
RuntimeScheduler is only used by TurboModule Manager in >RN0.72 #2461
tido64
merged 4 commits into
microsoft:main
from
shwanton:@shwanton/fix-turbomodule-adapter
Jun 16, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shwanton
changed the title
RCTAppSetupDefaultJsExecutorFactory doesn't take a _runtimeScheduler
Remove _runtimeScheduler param from RCTAppSetupDefaultJsExecutorFactory
Jun 14, 2023
tido64
reviewed
Jun 14, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing New Arch on 0.71! I thought we had tested this but apparently not 😅
shwanton
force-pushed
the
@shwanton/fix-turbomodule-adapter
branch
from
June 15, 2023 21:23
dca4803
to
2c08b5c
Compare
tido64
reviewed
Jun 15, 2023
tido64
approved these changes
Jun 16, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the time to fix this ❤️
shwanton
changed the title
Remove _runtimeScheduler param from RCTAppSetupDefaultJsExecutorFactory
RuntimeScheduler is only used by TurboModule Manager in >RN0.72
Jun 16, 2023
Closed
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When I was testing loading AsyncStorage as a TurboModule for macOS, I ran into this build error:
No matching function for call to 'RCTAppSetupDefaultJsExecutorFactory'
RuntimeScheduler
was added as a param toRCTAppSetupDefaultJsExecutorFactory
in RN Core herehttps://github.com/facebook/react-native/pull/36209/files#diff-1e16648bc876095f7583276815d1964d165986e1f5174ff23123c8c027a2ef0bR44
We could pick that change, or just remove the param till it's merged.
Test plan
CleanShot.2023-06-14.at.09.39.50.mp4