[PixPMusic]

Problem

The collapsed Material navigation rail can show an unintended bottom corner in Android Settings. Its background always used the expanded rail’s rounded shape; on chat screens the matching backdrop concealed it, while the retained sidebar’s darker surface exposed it in Settings.

Change

Scale the rail’s end-corner radius with its existing expansion progress. The collapsed rail is square regardless of its backdrop, and the expanded rail keeps its existing 16dp corners. The background and shadow use the same shape.

Scope and approval

Alex reported this visible defect and requested this focused fix. It corrects one Android rail shape and qualifies as a small fix for an obvious visual bug. No Settings container changes, new animation, preferences, contracts, providers, web/desktop, or iOS changes are needed. This PR is based on main after #25758 and has no stack dependency.

Verification

• vp run check:changed passed formatting and affected mobile/scripts typechecks. Targeted ktlint and detekt passed.
• Built and installed both native clients, then captured matching Settings → Appearance screens on an isolated Android 17.1 Fold8 emulator: 2448×1848, 420dpi, Iris dark, synthetic demo fixtures.
• The exposed collapsed corner now matches the rail fill. The expanded rail’s lower region is pixel-identical before and after.
• Verified expand/collapse and selecting Chats, Pull Requests, Usage, and Settings. No cosmetic UI test added. Physical devices were not exercised; this Kotlin-only change does not affect iOS or the phone’s bottom navigation.

Before	After

Expanded rail: before · after. Expand/collapse recording · Capture revisions, fingerprints, and asset hashes.

Model: GPT-6.1 Sol (high reasoning) | Harness: Codex in T3 Code

[macroscopeapp]

Approvability

Verdict: Approved at 224e1eb

Macroscope's review found this PR approvable — This is a small, self-contained Android visual bug fix that scales the existing rail corner shape with expansion progress. It preserves the expanded appearance and limits runtime impact to the rail’s background and shadow rendering.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: dc84b09
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: e23eb9f8-7dc1-4dc8-acf5-4fe2c7dfda47

Commits

Reviewing files that changed from the base of the PR and between dc84b09 and 224e1eb.

Files selected for processing: 1

• apps/mobile/modules/t3-native-controls/android/src/main/java/expo/modules/t3nativecontrols/T3WorkspaceNavigationModule.kt

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

Walkthrough

The navigation rail’s end-corner radius now scales with the animation fraction. The rail background and shadow use the interpolated shape. The fixed expanded-rail shape constant was removed.

Changes: Navigation Rail Shape

Layer / File(s)	Summary
Interpolate and apply rail shape apps/mobile/modules/t3-native-controls/android/src/main/java/expo/modules/t3nativecontrols/T3WorkspaceNavigationModule.kt	The end-corner radius now transitions from square to 16 dp based on the animation fraction. The background and shadow use this animated shape, replacing the fixed expanded shape.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Bug fix

Suggested labels: size:XS, 📱 Native Change

Suggested reviewers: juliusmarminge

Merge Risk: Minimal · up to 224e1

The Android rail shape change is narrowly scoped and ready to merge.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly and concisely describes the primary change: keeping the collapsed Android navigation rail square.
Description check		The description includes the required Problem, Change, Scope and approval, and Verification sections. It explains the defect, implementation, scope, test results, limitations, and UI evidence.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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