You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3dc8d96
Browse filesBrowse the repository at this point in the historyBrowse files
Isolate Activity Result support in its own Buck target
Summary:
Move Android Activity Result support out of the bridge target's aggregate source list and into a dedicated library. Reuse the bridge's lifecycle interface and inject an `ActivityResultRegistryProvider` plus an exception callback into the implementation. `ReactContext` owns registry discovery and lifecycle-listener registration, so the new target's only React bridge dependency is the bridge interfaces target.
Remove the individual source export shims, make the bridge depend on the new target, and give Activity Result tests direct friend access to the implementation target.
Changelog:
[Internal] - Isolate Android Activity Result support in its own build target
Differential Revision: D121859455
Copy file name to clipboardExpand all lines: packages/react-native/ReactAndroid/src/main/java/com/facebook/react/activityresult/DeferredActivityResultLauncher.kt
Copy file name to clipboardExpand all lines: packages/react-native/ReactAndroid/src/main/java/com/facebook/react/activityresult/ReactActivityResultCallerImpl.kt
Copy file name to clipboardExpand all lines: packages/react-native/ReactAndroid/src/test/java/com/facebook/react/activityresult/ReactActivityResultCallerImplTest.kt
Copy file name to clipboardExpand all lines: packages/react-native/ReactAndroid/src/test/java/com/facebook/react/activityresult/ReactActivityResultCallerThreadingTest.kt
0 commit comments