fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

fix(expo): recreate Android recomposer after reattach - #9143

Closed
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach
Closed

fix(expo): recreate Android recomposer after reattach#9143
D3OXY wants to merge 3 commits into
clerk:mainfrom
D3OXY:d3oxy/fix-expo-android-compose-reattach

Conversation

@D3OXY

@D3OXYD3OXY commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes#9142

Android native Clerk views cancel their parent Recomposer whenever the host temporarily detaches from its window. React Navigation can later reattach the same native view, leaving Compose content bound to a canceled parent composition context.

This change makes the shared Android host own the complete composition lifecycle:

  • setupView() ensures a live recomposer exists before setting Compose content, including when React Native Fabric updates props or measures content before window attachment;
  • window attachment recreates content for every Compose-backed Clerk view, including AuthView, UserButton, and UserProfileView;
  • window detachment disposes the composition and cancels and clears recomposer state;
  • recovery checks the launched recomposition job rather than its parent supervisor job.

iOS is unchanged.

Validation

  • Patched consumer app on Android API 36:
    • cold start → profile image and Account UI work;
    • details route → back → profile image and Account UI still work;
    • AI Chat tab → Home tab → profile image and Account UI still work;
    • repeated detach/reattach cycles remain interactive.
  • Verified the Fabric pre-attachment failure path no longer sets Compose content without first assigning a live parent recomposer.
  • pnpm --filter @clerk/expo... build
  • pnpm --filter @clerk/expo test — 92 tests passed
  • pnpm --filter @clerk/expo lint — no errors
  • pnpm --filter @clerk/expo format:check
  • Expo SDK 57 Android release fixture — BUILD SUCCESSFUL

Checklist

  • Full repository pnpm test runs as expected; targeted Expo tests pass.
  • Full repository pnpm build runs as expected; filtered Expo dependency build passes.
  • JSDoc is not applicable; no public API changed.
  • Documentation is not applicable; this restores intended lifecycle behavior.

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an Android issue where native UI components could crash before window attachment or become unresponsive after navigation and view reattach.
    • Improved Compose native view lifecycle handling by starting rendering only when attached to a window and properly disposing and canceling rendering on detachment to prevent stale state.

@vercel

vercelBot commented Jul 13, 2026

Copy link
Copy Markdown

@D3OXY is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@changeset-bot

changeset-botBot commented Jul 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c8bb8d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
NameType
@clerk/expoPatch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitaiBot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Android Compose native view host now defers recomposer creation until window attachment, recreates recomposition after reattachment, disposes composition state during detachment, and cancels stale resources. A Changesets entry records a patch release for @clerk/expo.

Changes

Expo Compose lifecycle

Layer / File(s)Summary
Lifecycle cleanup and restart entry points
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, packages/expo/android/src/main/java/expo/modules/clerk/ClerkUserButtonViewModule.kt
Compose setup no longer initializes the recomposer during construction. Recomposition starts from the host’s onAttachedToWindow(), while the UserButton-specific attachment override is removed. Detachment disposes the composition, cancels and clears recomposer resources, then invokes host detachment handling.
Recomposer recreation and release note
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt, .changeset/fuzzy-lions-recompose.md
startRecomposer() guards lifecycle state, creates a main-dispatcher recomposer, assigns it to composeView, launches recomposition, and records a patch release for @clerk/expo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels:expo

Suggested reviewers:wobsoriano

Poem

A bunny saw views detach and fly,
Then made fresh Compose bloom nearby.
Old jobs hopped out, new jobs began,
The button danced across the span.
“Reattach!” cried Bun, “and render bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Linked Issues check✅ PassedThe patch matches #9142 by disposing the old composition, clearing the canceled recomposer, and creating a fresh one on attach.
Out of Scope Changes check✅ PassedThe only added non-code change is a changeset entry, and the code edits stay focused on the Android recomposer lifecycle fix.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title accurately summarizes the main change: recreating the Android recomposer after reattachment.

Comment @coderabbitai help to get the list of available commands.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt (1)

27-27: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer importing kotlinx.coroutines.Job/SupervisorJob instead of fully-qualifying inline.

Fully-qualified references (kotlinx.coroutines.Job, kotlinx.coroutines.SupervisorJob) are repeated across the field declaration and startRecomposer(); importing them would improve readability.

Also applies to: 46-46, 54-54, 62-63, 65-65

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`
at line 27, Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Around line 53-67: Update startRecomposer so recomposerJob references the Job
returned by the coroutine launched to run
newRecomposer.runRecomposeAndApplyChanges(), rather than the standalone
SupervisorJob in the scope context. Preserve the existing scope and recomposer
setup, while ensuring the isActive guard permits recovery after the
recomposition coroutine completes or fails.
- Around line 53-67: Update ClerkAuthNativeView and ClerkUserProfileNativeView
so onAttachedToWindow() invokes setupView(), matching ClerkUserButtonNativeView.
Preserve the existing OnViewDidUpdateProps behavior and ensure reattaching
without prop changes recreates the Compose content after the recomposer
restarts.
---
Nitpick comments:
In
`@packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt`:
- Line 27: Replace the fully qualified kotlinx.coroutines.Job and
kotlinx.coroutines.SupervisorJob references in ClerkComposeNativeViewHost,
including recomposerJob and startRecomposer(), with imports at the top of the
file. Preserve the existing coroutine behavior and declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c8505747-f658-4f76-b111-5055c5f794dd

📥 Commits

Reviewing files that changed from the base of the PR and between 1d0e78c and fbfa349.

📒 Files selected for processing (2)
  • .changeset/fuzzy-lions-recompose.md
  • packages/expo/android/src/main/java/expo/modules/clerk/ClerkComposeNativeViewHost.kt

@pkg-pr-new

Copy link
Copy Markdown

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@9143

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@9143

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@9143

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@9143

@clerk/electron

npm i https://pkg.pr.new/@clerk/electron@9143

@clerk/electron-passkeys

npm i https://pkg.pr.new/@clerk/electron-passkeys@9143

@clerk/eslint-plugin

npm i https://pkg.pr.new/@clerk/eslint-plugin@9143

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@9143

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@9143

@clerk/express

npm i https://pkg.pr.new/@clerk/express@9143

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@9143

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@9143

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@9143

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@9143

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@9143

@clerk/react

npm i https://pkg.pr.new/@clerk/react@9143

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@9143

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@9143

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@9143

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@9143

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@9143

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@9143

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@9143

commit: c8bb8d5

@wobsorianowobsoriano left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reporting #9142! I reproduced it on a fresh SDK 57 app (UserButton in a Stack header via android emulator) and confirmed this PR fixes the reattach bug. But with this PR applied I got a crash on cold start, before ever navigating:

IllegalStateException: Cannot locate windowRecomposer; View ComposeView{...} is not attached to a window
onMeasure (ComposeView.android.kt:475)
updateLayout (SurfaceMountingManager.kt:829)

Did you test this locally? Can you confirm my comment here makes sense? https://github.com/clerk/javascript/pull/9143/changes#r3595667616

}
}
addView(view, LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT))
}

@wobsorianowobsorianoJul 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got a cold-start crash when testing this. Adding the recomposer creation back at construction fixed the cold-start crash for me:

Suggested change
}
}
init {
startRecomposer()
}

@wobsoriano

Copy link
Copy Markdown
Member

Thank you again! I'll close this in favor of #9178 (added you as co-author)

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Expo] Android native UserButton becomes inert after navigation detach

2 participants

@D3OXY@wobsoriano