From 9729f05d9c89947f56cc9f6f5fa85635133176f7 Mon Sep 17 00:00:00 2001 From: os-zhuang Date: Thu, 11 Jun 2026 09:59:55 +0500 Subject: [PATCH] fix(ios): drop NativeWind ring-* from Input focus state (crashed on native) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Focusing any `Input` on iOS threw "Couldn't find a navigation context" and blanked the screen. Bisected on the iPhone 17 simulator: a bare `TextInput` focuses fine, but our `Input` does not — the difference is the focus state toggling the `ring-1 ring-ring` NativeWind utilities. Those ring utilities blow up when applied on native iOS (the error is mis-reported as a navigation-context failure). `border-ring` alone gives a clear focus indicator (blue border) and works cleanly. This blocked the Connect / Sign-In screens — and every text field — on iOS. Found and fixed via Simulator testing; verified the full flow end-to-end on device (Connect → Sign In → Dashboard) with no redbox after the change. The Input snapshot test still passes (it captures the unfocused state). Co-Authored-By: Claude Opus 4.8 (1M context) --- components/ui/Input.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/ui/Input.tsx b/components/ui/Input.tsx index 500396a..83d3f48 100644 --- a/components/ui/Input.tsx +++ b/components/ui/Input.tsx @@ -24,7 +24,7 @@ export const Input = React.forwardRef(