Title: Android: Frame navigation stalls after activity.recreate() · Issue #11591 · NativeScript/NativeScript · GitHub
Open Graph Title: Android: Frame navigation stalls after activity.recreate() · Issue #11591 · NativeScript/NativeScript
X Title: Android: Frame navigation stalls after activity.recreate() · Issue #11591 · NativeScript/NativeScript
Description: Environment @nativescript/core 9.1.1, @nativescript/android 9.1.1 Reproduced on Android emulators running API 35 and API 37 Describe the bug After the activity is recreated programmatically with activity.recreate(), the root Frame stops ...
Open Graph Description: Environment @nativescript/core 9.1.1, @nativescript/android 9.1.1 Reproduced on Android emulators running API 35 and API 37 Describe the bug After the activity is recreated programmatically with ac...
X Description: Environment @nativescript/core 9.1.1, @nativescript/android 9.1.1 Reproduced on Android emulators running API 35 and API 37 Describe the bug After the activity is recreated programmatically with ac...
Opengraph URL: https://github.com/NativeScript/NativeScript/issues/11591
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Android: Frame navigation stalls after activity.recreate()","articleBody":"### Environment\n\n- `@nativescript/core` 9.1.1, `@nativescript/android` 9.1.1\n- Reproduced on Android emulators running API 35 and API 37\n\n### Describe the bug\n\nAfter the activity is recreated programmatically with `activity.recreate()`, the root Frame stops processing navigation. `frame.goBack()` and `frame.navigate()` add an entry to the navigation queue, but it never runs. The system back button then finishes the activity: the queued back entries count against `canGoBack()`, so the frame reports nothing to go back to.\n\nActivity recreation caused by a system configuration change (for example, a font scale change) does not have this problem.\n\n### Cause\n\nThe recreated activity attaches the Frame's new native view while its lifecycle is still `INITIALIZED`, before `onCreate` has returned. `Frame._onAttachedToWindow` returns early in that state:\n\n```ts\nconst lifecycleState = activity?.getLifecycle?.()?.getCurrentState() || androidx.lifecycle.Lifecycle.State.CREATED;\nif ((this._manager && this._manager.isDestroyed()) || !lifecycleState.isAtLeast(androidx.lifecycle.Lifecycle.State.CREATED)) {\n\treturn;\n}\nthis._attachedToWindow = true;\nthis._isReset = false;\nthis._processNextNavigationEntry();\n```\n\nNo other attach event follows, so `_isReset` stays `true` and `_attachedToWindow` stays `false`. `_processNextNavigationEntry` then returns early on `this._isReset && !this._attachedToWindow` for every later navigation.\n\nTrace from wrapping the Frame methods (`activity` is the window's activity, which is also the current activity at every step):\n\n```\nrecreate()\ndisposeNativeView before: activity=DESTROYED isReset=false\n_onRootViewReset after: attachedToWindow=false isReset=true\ninitNativeView before: activity=INITIALIZED isReset=true\n_onAttachedToWindow before: activity=INITIALIZED isReset=true\n_onAttachedToWindow after: attachedToWindow=false isReset=true \u003c- guard bails\nframe.goBack() queue=1 executing=false isReset=true attachedToWindow=false\nframe.goBack() queue=2 executing=false isReset=true attachedToWindow=false\n```\n\nWith a font-scale change instead, the attach arrives once the activity is `RESUMED` and navigation keeps working:\n\n```\n_onAttachedToWindow before: activity=RESUMED isReset=true\n_onAttachedToWindow after: attachedToWindow=true isReset=false\n```\n\n### To reproduce\n\n1. Use a `Frame` as the root view and navigate forward at least once.\n2. Call `recreate()` on the window's activity, for example `frame.getNativeWindow().android.activity.recreate()`.\n3. Call `frame.goBack()`, or press the system back button.\n\n**Expected:** the frame navigates back.\n**Actual:** nothing happens. The system back button closes the app.\n\n### Possible fix\n\nWhen the guard rejects the attach because the activity isn't `CREATED` yet, the frame could retry once the activity's lifecycle reaches `CREATED`, for example through a lifecycle observer or by posting to the native view, instead of waiting for an attach event that never comes.\n\n### Additional context\n\nI found this while testing nativescript-vue's handling of recreated windows (nativescript-vue/nativescript-vue#1187). The traces above come from that demo app, but the stall is in core and plain `frame.goBack()` hits it too.\n","author":{"url":"https://github.com/rigor789","@type":"Person","name":"rigor789"},"datePublished":"2026-10-26T13:15:51Z","url":"https://github.com/NativeScript/NativeScript/issues/11591"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:e6332ea9-91d2-f16d-0af4-6afffd6ca26d |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A140:A71F9:BD9A4F:EE6845:6B013322 |
| html-safe-nonce | 1d796bc0a399ac69f5b43b17f16565c1dcc705d7277b98e72a4cd5fc80a62ec8 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBMTQwOkE3MUY5OkJEOUE0RjpFRTY4NDU6NkIwMTMzMjIiLCJ2aXNpdG9yX2lkIjoiMTY3MDY4NjAzMzA0NzUzMjMyMiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 4f20e5352738fbea0d5deffe4e40515d8fce2e2b3804f7836c71f05bf67ebf87 |
| hovercard-subject-tag | issue:6040415274 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/NativeScript/NativeScript/11591/issue_layout |
| twitter:image | https://opengraph.githubassets.com/4ddfc1eed52dd11c2718dcbb4ea558ea10927c2196e96d7ada5b09b68b6065c4/NativeScript/NativeScript/issues/11591 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/4ddfc1eed52dd11c2718dcbb4ea558ea10927c2196e96d7ada5b09b68b6065c4/NativeScript/NativeScript/issues/11591 |
| og:image:alt | Environment @nativescript/core 9.1.1, @nativescript/android 9.1.1 Reproduced on Android emulators running API 35 and API 37 Describe the bug After the activity is recreated programmatically with ac... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | rigor789 |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/NativeScript/NativeScript git https://github.com/NativeScript/NativeScript.git |
| octolytics-dimension-user_id | 7392261 |
| octolytics-dimension-user_login | NativeScript |
| octolytics-dimension-repository_id | 31492490 |
| octolytics-dimension-repository_nwo | NativeScript/NativeScript |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 31492490 |
| octolytics-dimension-repository_network_root_nwo | NativeScript/NativeScript |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | canary-2 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width