[YevheniiKotyrlo]

Summary:

When Android ends a backgrounded app's process but keeps its task, a link to the app relaunches it into that task: Android recreates the activity from the task's first intent and hands the link to onNewIntent. That happens before the React context exists, so ReactHostImpl.onNewIntent drops the intent ("Tried to access onNewIntent while context is not ready") and no url event fires. IntentModule.getInitialURL() then reads currentActivity.intent, which still holds the task's first link.

ReactActivity.onNewIntent now calls setIntent(intent) first, as Activity.onNewIntent describes for an activity whose getIntent() should return the new intent, so Linking.getInitialURL() answers the link that relaunched the app. A running app still receives the link as a url event; a later getInitialURL() call answers that link rather than the launch link.

Fixes #59006

Changelog:

[ANDROID] [FIXED] - Linking.getInitialURL() returns the link that relaunched an app whose process Android ended, instead of the task's first link

Test Plan:

• ./gradlew :packages:react-native:ReactAndroid:testDebugUnitTest --tests "com.facebook.react.ReactActivityTest" -Preact.internal.useHermesStable=true: three new tests. Without the change two fail — the activity's intent stays rntester://first after onNewIntent delivers rntester://second, and getInitialURL() resolves the first link. The third, a launch with no later link, passes either way.
• ./gradlew :packages:react-native:ReactAndroid:testDebugUnitTest :packages:react-native:ReactAndroid:compileReleaseKotlin :packages:react-native:ReactAndroid:compileReleaseJavaWithJavac -PenableWarningsAsErrors=true -Preact.internal.useHermesStable=true: 724 tests in 104 suites, 0 failures, and the release sources compile.
• node ./scripts/format-java.js --check and node ./scripts/format-kotlin.js --check pass.
• RNTester on an Android 16 emulator, before and after: open rntester://example/ButtonExample, background the app until am kill ends its process with the task still in Recents, then open rntester://example/SwitchExample. Without the change RNTester comes back on the Button page; with it, on the Switch page. Both runs log "Tried to access onNewIntent while context is not ready", so getInitialURL() is what carries the link.
• The debug RNTester builds pass with -PenableWarningsAsErrors=true; the rest of build_android was not run.

[YevheniiKotyrlo]

Device evidence — before / after

UNFIXED — after the process is killed with the task kept in Recents, rntester://example/SwitchExample relaunches RNTester on the Button page, the link that opened the task.

FIXED — the same relaunch opens the Switch page.

before — main at 977ca0a204	after — with this PR

RNTester debug builds from main at 977ca0a204 with and without this change, embedded bundle, on an Android 16 (API 36) emulator, 1140×2400 at density 480. Each run opens rntester://example/ButtonExample, goes Home, opens Settings, goes Home, runs am kill com.facebook.react.uiapp until pidof prints nothing, checks the task is still in dumpsys activity recents, and opens rntester://example/SwitchExample. Both builds log "Tried to access onNewIntent while context is not ready" on the relaunch.