Skip to content

Remove obsolete Android Fabric surface paths (#59036) - #59036

Open
javache wants to merge 2 commits into
react:mainfrom
javache:export-D124979204
Open

javache wants to merge 2 commits into
react:mainfrom
javache:export-D124979204

Conversation

@javache

@javache javache commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary:

ReactInstanceManager can no longer initialise the legacy bridge, so the bridge+Fabric surface lifecycle JNI entry points are unreachable. Remove those methods while retaining the existing UIManager signatures as explicit unsupported/no-op compatibility overrides, and simplify native surface tracking to weak Java-owned SurfaceHandlers.

Changelog: [Internal]

Reviewed By: christophpurrer

Differential Revision: D124979204

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 13, 2026
@meta-codesync

meta-codesync Bot commented Oct 13, 2026

Copy link
Copy Markdown

@javache has exported this pull request. If you are a Meta employee, you can view the originating Diff in D124979204.

Summary:
The View-based `UIManager` lifecycle predates `ReactHost` and `ReactSurface` and is no longer used by the supported architecture. Deprecate these methods before their planned removal and point callers to `ReactHost.createSurface(...)` and `ReactSurface.start()` or `stop()`.

Changelog:
[Android][Deprecated] - Deprecate the legacy View-based surface lifecycle methods in `UIManager`.

Differential Revision: D124990160
@meta-codesync meta-codesync Bot changed the title Remove obsolete Android Fabric surface paths Remove obsolete Android Fabric surface paths (#59036) Oct 13, 2026
javache added a commit to javache/react-native that referenced this pull request Oct 13, 2026
Summary:

ReactInstanceManager can no longer initialise the legacy bridge, so the bridge+Fabric surface lifecycle JNI entry points are unreachable. Remove those methods while retaining the existing UIManager signatures as explicit unsupported/no-op compatibility overrides, and simplify native surface tracking to weak Java-owned SurfaceHandlers.

Changelog: [Internal]

Reviewed By: christophpurrer

Differential Revision: D124979204
Summary:
Pull Request resolved: react#59036

ReactInstanceManager can no longer initialise the legacy bridge, so the bridge+Fabric surface lifecycle JNI entry points are unreachable. Remove those methods while retaining the existing UIManager signatures as explicit unsupported/no-op compatibility overrides, and simplify native surface tracking to weak Java-owned SurfaceHandlers.

Changelog: [Internal]

Reviewed By: christophpurrer

Differential Revision: D124979204

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported p: Facebook Partner: Facebook Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant