Android ReactActivity Destroy Prevents Successful OnActivityResult Calls
还没有人认领这个 Issue。
- 主要语言
- C++
- 星标
- 127k
- 派生
- 25.3k
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 4
描述
Description
If a native module opens an activity that redirects out of the application and the application is killed in the background by the Android OS, the react context is lost and the native module's activity is unable to call onActivityResult.
If the redirect from the third party app is back to the activity in the native module, the ReactActivity is not created at this point. When the native activity then sets result and finishes to return back to the ReactActivity the ReactActivity has to start up.
Originally reported: https://github.com/facebook/react-native/issues/30277
Steps to reproduce
Building the App
cd ReproducerApp
npm install
npm start
npm run android
Reproduction Steps
- Run the app on an Android device
- Tap the "Open Activity" button
- In the second activity, tap "Go to Web" to open Google in a browser
- Use the following command to forcibly kill the app:
adb shell am kill com.reproducerapp - Resume the activity with:
adb shell am start -n com.reproducerapp/.RedirectActivity -d "redirect://crash" - Tap "Return Result" in the activity
- Check logcat for missing "RESULT" and "Completed" logs
Expected Behavior
When returning to the app after it's been killed, the callback should work and you should see "RESULT" and "Completed" in the logs.
Actual Behavior
When the app is killed and then restored, the activity result is processed before React Native is ready. The JavaScript callback is not executed, and you won't see "RESULT" or "Completed" logs, indicating the callback was lost.
React Native Version
0.79.2
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: macOS 15.5
CPU: (10) arm64 Apple M1 Max
Memory: 268.70 MB / 32.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 18.20.8
path: ~/.nvm/versions/node/v18.20.8/bin/node
Yarn:
version: 1.22.19
path: /opt/homebrew/bin/yarn
npm:
version: 10.9.2
path: ~/.nvm/versions/node/v18.20.8/bin/npm
Watchman:
version: 2025.04.28.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK: Not Found
Android SDK:
API Levels:
- "30"
- "31"
- "32"
- "33"
- "33"
- "34"
- "35"
Build Tools:
- 28.0.3
- 29.0.2
- 30.0.2
- 30.0.3
- 33.0.1
- 34.0.0
- 34.0.0
- 35.0.0
- 35.0.0
- 36.0.0
System Images:
- android-26 | Google APIs ARM 64 v8a
- android-27 | ARM 64 v8a
- android-27 | Google Play Intel x86 Atom
- android-28 | ARM 64 v8a
- android-28 | Google APIs ARM 64 v8a
- android-28 | Google ARM64-V8a Play ARM 64 v8a
- android-29 | Google APIs ARM 64 v8a
- android-29 | Google Play ARM 64 v8a
- android-30 | Google Play ARM 64 v8a
- android-31 | Google Play ARM 64 v8a
- android-33 | Google APIs ARM 64 v8a
- android-34 | Google Play ARM 64 v8a
- android-35 | Google APIs ARM 64 v8a
- android-35 | Google Play ARM 64 v8a
- android-UpsideDownCake | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2024.3 AI-243.24978.46.2431.13363775
Xcode:
version: /undefined
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.8
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 18.0.0
wanted: 18.0.0
react:
installed: 19.0.0
wanted: 19.0.0
react-native:
installed: 0.79.2
wanted: 0.79.2
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: Not found
newArchEnabled: false
info React Native v0.80.0 is now available (your project is running on v0.79.2).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.80.0
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.79.2&to=0.80.0
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos".
Stacktrace or Logs
unknown:ReactHost com.reproducerapp E Unhandled SoftException (Ask Gemini)
com.facebook.react.bridge.ReactNoCrashSoftException: raiseSoftException(onActivityResult(activity = "com.reproducerapp.MainActivity@1afbd28", requestCode = "100", resultCode = "-1", data = "Intent { (has extras) }")): Tried to access onActivityResult while context is not ready
at com.facebook.react.runtime.ReactHostImpl.raiseSoftException(ReactHostImpl.java:1025)
at com.facebook.react.runtime.ReactHostImpl.raiseSoftException(ReactHostImpl.java:1018)
at com.facebook.react.runtime.ReactHostImpl.onActivityResult(ReactHostImpl.java:776)
at com.facebook.react.ReactDelegate.onActivityResult(ReactDelegate.java:187)
at com.facebook.react.ReactActivityDelegate.onActivityResult(ReactActivityDelegate.java:192)
at com.facebook.react.ReactActivity.onActivityResult(ReactActivity.java:79)
at android.app.Activity.onActivityResult(Activity.java:7571)
at android.app.Activity.internalDispatchActivityResult(Activity.java:9470)
at android.app.Activity.dispatchActivityResult(Activity.java:9447)
at android.app.ActivityThread.deliverResults(ActivityThread.java:6025)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:5454)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:5500)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:73)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:63)
at android.app.servertransaction.TransactionExecutor.executeLifecycleItem(TransactionExecutor.java:169)
at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:101)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2773)
at android.os.Handler.dispatchMessage(Handler.java:109)
at android.os.Looper.loopOnce(Looper.java:232)
at android.os.Looper.loop(Looper.java:317)
at android.app.ActivityThread.main(ActivityThread.java:8934)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911)
MANDATORY Reproducer
https://github.com/melissaosullivan/rn-activity-destroy-state-lost-repro/tree/main
Screenshots and Videos
No response
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
使用必需的 ReproducerApp 命令重现所描述的生命周期,然后跟踪从 ReactActivity.onActivityResult 经过 ReactActivityDelegate、ReactDelegate 到 ReactHostImpl.onActivityResult 的调用栈。确认结果是在 React context 准备就绪之前传递的,并且完成的流程会产生缺失的 RESULT 和 Completed 日志。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- android, java
- 领域
- mobile-dev
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100