Summary:
For these values we're not using dynamic values. We can statically
compile in the values we're running.
DiffTrain build for commit https://github.com/facebook/react/commit/df12d7eac40c87bd5fdde0aa5a739bce9e7dce27.
Reviewed By: tyao1
Differential Revision: D45751304
Pulled By: kassens
fbshipit-source-id: d00e441ab75bf8fe038bb0e80eeb392421344657
Summary:
When I was renaming the next channel to canary, I updated the
`publish_preleases` workflow correctly, but I skipped over
`publish_preleases_nightly`. Oops.
DiffTrain build for commit https://github.com/facebook/react/commit/7cd98ef2bcbc10f164f778bade86a4daeb821011.
Reviewed By: mofeiZ
Differential Revision: D45720403
fbshipit-source-id: 13ab5d0d0af6cc899944507249b39b03adbcb994
Summary:
The idea is that the default `yarn test` command should be the one that
includes the most bleeding edge features, because during development you
probably want as many features enabled as possible.
That used to be `www-modern` but nowadays it's `experimental` because
we've landed a bunch of async actions stuff in experimental but it isn't
yet being tested at Meta.
So this switches the default to `experimental`.
DiffTrain build for commit https://github.com/facebook/react/commit/b5810163e913e8c95a7a0a6dee039bc102e3c987.
Reviewed By: mofeiZ
Differential Revision: D45719891
fbshipit-source-id: 7c820b8b546f1c90bb3d77993befde86e42d399b
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37349
X-link: https://github.com/facebook/yoga/pull/1288
Fixes https://github.com/facebook/yoga/issues/1283
New versions of CMake add "policies" which control how the build system acts wrt breaking changes. By default, CMake will emulate the behavior of the version specified in `cmake_minimum_required`.
Setting a policy to true (to opt into new behavior where `cmake_minimum_required` is lower than the current version) seems actually just error out on the old versions.
Googling around, apparently the way I should be doing this is to specify `<policy_max>` as part of `cmake_minimum_required `. https://gitlab.kitware.com/cmake/cmake/-/issues/20392
This should I think use new policies introduced up to 3.26 (what we test on right now), while letting 3.13 be the minimum.
Reviewed By: cortinico
Differential Revision: D45724864
fbshipit-source-id: 120cc2015a043605e7c07ef0459667643a4284b7
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37441
Changelog: [Internal]
i just noticed that `[_delegate createContextContainer]` can be null because it returns `shared_ptr`, we should protect against that!
Reviewed By: javache
Differential Revision: D45805196
fbshipit-source-id: 645815812da1718e1025c7e6b2763e698d86b59a
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37442
Changelog: [Internal]
this better describes what's going on and is more standard obj-c
Reviewed By: javache
Differential Revision: D45805034
fbshipit-source-id: d8e5938c856f356ce96a3f6d393eaddbb02aa555
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37396
Pull Request resolved: https://github.com/facebook/react-native/pull/37368
## Changes
This diff hooks up global.nativeModuleProxy to the TurboModule interop layer.
Now, when you call NativeModules.Foo, the TurboModule system will create the Foo legacy module, and return it to JavaScript.
## Example
global.nativeModuleProxy.Foo:
- ObjC++: Use RCTTurboModuleManager to create the ObjC legacy module for Foo
- C++: Use the ObjC legacy modules to create and return a ObjCInteropTurboModule object to JavaScript.
Changelog: [Internal]
Reviewed By: cipolleschi
Differential Revision: D45781152
fbshipit-source-id: 9059cd0de294aa17dcbf120322d7e86e7c7a83ed
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37395
Pull Request resolved: https://github.com/facebook/react-native/pull/37364
When the TurboModule interop layer is enabled, it should create modules that conform to RCTBridgeModule (i.e: legacy and turbo modules).
When the TurboModule interop layer is disabled, it should only create modules that conform to RCTTurboModule (i.e: turbo modules).
Changelog: [Internal]
Reviewed By: cipolleschi
Differential Revision: D45781155
fbshipit-source-id: 2bf2c6cdbe0db99a57fce0d0c21c66aee3465e0d
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37391
This was accidentally set to true by default.
This resulted in the TurboModule interop layer being enabled on Standalone apps.
Changelog: [Internal]
Reviewed By: dmytrorykun
Differential Revision: D45783832
fbshipit-source-id: e88f2bc8cba06356b9caab2ba25bcdd9da82b37e
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37415
Previously, when focusing on an unchecked checkbox in React Native Paper with VoiceOver, it was announcing as "not selected". iOS voiceover uses "unselected" instead ("not selected" is used on Android Talkback). Update code to use "unselected".
Changelog: [Internal]
Reviewed By: cipolleschi
Differential Revision: D45799922
fbshipit-source-id: 30f7813ed9f1fdad817e18b28c4fcf99cb4b884f
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37414
Previously, when focusing on a checkbox or radio button in React Native Fabric with VoiceOver, it wasn't announcing the role, e.g. "checkbox". Instead it would just say [label][state], e.g. "Automatically check for updates, unchecked". This is an extremely confusing experience for screen reader users because they don't know what kind of element they are focusing, including how to interact with it.
"checkbox" and "radio button" aren't recognized as [Apple iOS traits](https://developer.apple.com/documentation/uikit/uiaccessibilitytraits?language=objc), but we'd like to have consistency with the mobile safari experience.
Reviewed By: cipolleschi
Differential Revision: D45797554
fbshipit-source-id: 418e73342aaa8d0986e330bfd54078be27d3491f
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37272
This change enables some tests on RNTester and on the Template to verify that we won't be breaking `use_frameworks!` again in the future.
## Changelog:
[iOS][Added] - Add tests to check use frameworks with dynamic linking.
Reviewed By: cortinico
Differential Revision: D45605977
fbshipit-source-id: 06f05aba427e78a7bb1d8dc835fa83d8550586db
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37273
When using dynamic frameworks, we can't rely on Codegen to register all the components into the renderer. That's because, we would have to codegen a new target, which depends on ALL the 3rd party dependencies that expose a UI component.
The previous PR adds support for distributed automatic registration when components are loaded in memory.
However, not to slow down the adoption of the New Architecture, there could be apps that need to register a component that does not support the distributed approach yet. Thanks to this method, apps can register those components.
## Changelog:
[iOS][Added] - Added a mechanism to register components into the renderer from the user app.
Reviewed By: dmytrorykun
Differential Revision: D45605688
fbshipit-source-id: 3583913f2700be4d6cb33a862429486aca675acf
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37274
With dynamic frameworks, we can't use floating C functions.
The way in which dynamic frameworks work is that they need to be self contained. They are built in isolation so that other frameworks can be linked against them to solve their dependencies.
Currently, when working with 3rd party libraries, we are Codegenerating a RCTThirdPartyComponentProvider which tries to invoke floating C functions that are defined in other modules. React-RCTFabric has no visibility on those modules, therefore it fails building.
The implemented solution exclude the generation of those symbols and leverage a the Objective-C runtime to automatically register libraries when they are loaded.
**This mechanism is applied ONLY when the flag RCT_DYNAMIC_FRAMEWORKS is turned on.** There will be no impact on internal meta apps, nor on any apps that are not using Dynamic Frameworks.
This change requires a small migration in all the Fabric components libraries that wants to support dynamic frameworks. They have to implement a
```
+ (void)load
{
[super load];
}
```
method in their ComponentView.
Not to slow down the adoption of the new architecture, waiting for a migration in the ecosystem, the next diff introduce a secondary, declarative loading mechanism for Fabric Components, which follows the same approach used by TurboModules.
## Changelog:
[iOS][Changed] - Add support for distributed registration of Fabric Components with Dynamic Libraries.
Notes that this change is NOT breaking as dynamic frameworks were not working before in the New Architecture. Static Libraries and Static Frameworks continue working as usual.
Reviewed By: dmytrorykun
Differential Revision: D45605441
fbshipit-source-id: e609fbf6f92fddfbaa676227fde60962d6b0faa4
Summary:
Fix the logic error when setPadding int ReactTextView.
## Changelog:
<!-- Help reviewers and the release process by writing your own changelog entry.
Pick one each for the category and type tags:
[ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message
For more details, see:
https://reactnative.dev/contributing/changelogs-in-pull-requests
Pull Request resolved: https://github.com/facebook/react-native/pull/36999
Reviewed By: NickGerleman
Differential Revision: D45773288
Pulled By: javache
fbshipit-source-id: ed4681aeab58ed4c3d2e04edb2d096b50932c088
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37306
### Stack
ARIA roles in React Native are implemented on top of accessibilityRole. This is lossy because there are many more ARIA roles than accessibilityRole. This is especially true for RN on desktop where accessibilityRole was designed around accessibility APIs only available on mobile.
This series of changes aims to change this implementation to instead pass the ARIA role to native, alongside any existing accessibilityRole. This gives the platform more control in exactly how to map an ARIA role to native behavior.
As an example, this would allow mapping any ARIA role to AutomationControlType on Windows without needing to fork to add new options to accessibilityRole.
It also allows greater implementation flexibility for other platforms down the line, but for now, iOS and Android behave the same as before (though with their implementation living in native).
### Diff
This replicates the roles to Java. When using MapBuffer we pass the role by ordinal, assuming they keep in sync. We otherwise still pass by string matching the JS side.
Previous implementation kept `accessibilityRole` on a view tag of the native view. This adds `role` as a view tag as well.
For now, to reuse the existing code, we then expose a single function to query `AccessibilityRole` from the combined view tags. This will do the same mapping previously done in JS, so that any code previously reading for an `AccessibilityRole` will now get one derived from the role view tag if present.
Changelog: [Internal]
Reviewed By: sammy-SC
Differential Revision: D45431381
fbshipit-source-id: a72c7880d41b5cf2c4e1c1f3ebfa6832ce8b4250
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37305
### Stack
ARIA roles in React Native are implemented on top of `accessibilityRole`. This is lossy because there are many more ARIA roles than `accessibilityRole`. This is especially true for RN on desktop where `accessibilityRole` was designed around accessibility APIs only available on mobile.
This series of changes aims to change this implementation to instead pass the ARIA role to native, alongside any existing `accessibilityRole`. This gives the platform more control in exactly how to map an ARIA role to native behavior.
As an example, this would allow mapping any ARIA role to [`AutomationControlType`](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.peers.automationcontroltype?view=windowsdesktop-7.0&viewFallbackFrom=dotnet-uwp-10.0) on Windows without needing to fork to add new options to `accessibilityRole`.
It also allows greater implementation flexibility for other platforms down the line, but for now, iOS and Android behave the same as before (though with their implementation living in native).
### Diff
This syncs the Fabric representations of Roles to the current state of the world in JS, and adds usage to the view configs.
1. `Role` enum for the View `role` prop (ARIA role)
2. Sync enums and conversions to JS `AccessibilityRole`
1. This parsing is done for `TextAttributes` only. `View` uses the string directly
2. Add ARIA roles, and parse those to their enum form.
3. Move enums from attributedstring primitves to accessibility primitives
3. Add to viewconfig to allow it to be passed
Changelog: [Internal]
Reviewed By: sammy-SC
Differential Revision: D45431372
fbshipit-source-id: 0150538345bbb6cb4d9426c4eebd0f67c2a33f3d
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37377
For 0.72 I enabled `moduleResolution: "nodenext"` which allows some package exports support, but this is imperfect. E.g. RN will typecheck against the `node` condition and there are some more restrictions than we need.
D45720238 bumped TypeScript to 5.0 for RN 0.73, along with D45721088 which brought the tsconfig inline. This lets us switch to the new [`moduleResolution: "bundler"`](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#moduleresolution-bundler) and instructs `tsc` to follow the `react-native` export condition.
See even more context at: https://github.com/microsoft/TypeScript/pull/51669
Changelog:
[General][Added] - Better TypeScript support for package.json exports field
Reviewed By: christophpurrer
Differential Revision: D45769740
fbshipit-source-id: 1ad450b8157bfd0d539289835bed097fd950cf78
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37422
Changelog: [Internal]
in this simple change, i renamed the `preload` API, which triggers all the rct instance / javascript runtime creation to `start`. `preload` is a confusing API on the host because the host should be agnostic of when the timing to create its dependencies are, and the consumer should determine when initialization is lazy, early, etc.
Reviewed By: cipolleschi
Differential Revision: D45760583
fbshipit-source-id: bea26d21f950474352280292426a5facbe52b60f
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37327
Changelog: [Internal]
in this diff, we enforce at the API level that the `RCTHostDelegate` is not responsible for creating the js engine instance.
Reviewed By: cipolleschi
Differential Revision: D45596321
fbshipit-source-id: 7862344d8b42e9d70e7fb7c7e9980953f0d66a8b
Summary:
The core implementation for ShadowNode's `getDebugProps` lives in ConcreteViewShadowNode, but is not actually specific to that class. Additionally, `LayoutableShadowNode` overrides `getDebugProps` in a way that doesn't concat props from its base class. Instead, override the method properly so we only need the implementation in `LayoutableShadowNode`.
Changelog: [Internal]
Reviewed By: sammy-SC
Differential Revision: D45729105
fbshipit-source-id: 946d8d97b86fde0488527ce00db5a019c95e31af
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37328
Changelog: [Internal]
in this diff, i introduced a C function to be used to create RCTHost that obfuscates away all the C++ arguments. i expect this to be the API that the vast majority of the community will use to create `RCTHost`.
Reviewed By: cipolleschi
Differential Revision: D45678970
fbshipit-source-id: e3479db1bb68d93b3ee2f02598413d2080bb5ea9
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37344
Changelog: [Internal]
in this diff we do the following:
- pass an error handler that's responsible for bubbling up the error metadata from the react instance obj-c wrapper (RCTInstance) to the actual react instance (ReactInstance)
- parse the error metadata in RCTHost and pass it up to its delegate
Reviewed By: cipolleschi
Differential Revision: D45720132
fbshipit-source-id: 996c7c43ed6feb72596296eedac18e204b960426
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37343
Changelog: [Internal]
in this stack i address the `jsErrorHandlingFunc` argument in the constructor of `RCTHost`.
currently in userland, the delegate of `RCTHost` is responsible for the following if they want to handle the errors fired in C++ land:
- importing the C++ class MapBuffer
- creating a C++ lambda method
- parsing the MapBuffer
in this diff stack i simplify this so we only need to implement a delegate method where userland only receives Foundation types. yay!
bypass-github-export-checks
Reviewed By: RSNara
Differential Revision: D45720131
fbshipit-source-id: b5541abe505140b4b85cbec1a8acecc1a3df7a72
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37398
Changelog: [Internal]
in this diff, i introduce an internal category and header for RCTHost for functionality that needs to be accessible for our purposes, but not an official part of our stable API.
after this change, we can remove `ReactInstanceForwarding`.
Reviewed By: cipolleschi
Differential Revision: D45760091
fbshipit-source-id: 88a82fc70a20934f5d8989041c3eb2ffe2d27b20
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/37399
Changelog: [Internal]
in this stack, i remove the `ReactInstanceForwarding` protocol. it is super lean and is only used by two classes, and the polymorphic behavior never comes into play because we never have a pointer to `id<ReactInstanceForwarding>` in our codebase.
being able to call into JS from native is tablestakes behavior in userland, so i'm moving that to the public API. i also renamed it to be more clear that it's calling from native into JS, not the other way around.
Reviewed By: cipolleschi
Differential Revision: D45760090
fbshipit-source-id: 8ac99723796cb65891076e8e7d69aeefe3e94213
Summary:
X-link: https://github.com/facebook/yoga/pull/1294
Pull Request resolved: https://github.com/facebook/react-native/pull/37383
Add -Wextra to the build, and fixup some more instances of -Wunused-parameter that it sufaces which were not automatically fixable.
Reviewed By: javache
Differential Revision: D45772846
fbshipit-source-id: 29bf71006f63161521fe5869c3a7d8bf7aae9c81
Summary:
X-link: https://github.com/facebook/yoga/pull/1291
Pull Request resolved: https://github.com/facebook/react-native/pull/37371
This makes React Native use `libyogacore` as provided by Yoga's reference CMake build. This in turn matches Yoga in the OSS RN build to the same compilation settings we use internally. It also means less differences between all the builds (maintainability win).
This does not yet do the same for the Yoga JNI bindings.
Changelog:
[Android][Changed] - Use reference Yoga CMake Build
Reviewed By: cortinico
Differential Revision: D45764537
fbshipit-source-id: 1aafd221d2afa994b6efae3c267ee7ffbdf0faad
kassens (Meta Employee)
acdlite
Pieter De Baets
Nick Gerleman
Phillip Pan
Ramanpreet Nara
Patryk Ozga
Carmen Krol
Riccardo Cipolleschi
jcdhlzq
Intl Scheduler
Junfeng Li
Pieter Vanderwerff
Samuel Susla
Luna Wei