Can we access your project?
Current Behavior
When a page configured as the "Logged In Page" (Settings & Integrations > General > Initial Page) uses a Custom Nav Bar Component as its Nav Bar Style, the automatic redirect on successful sign-in described in the documentation ("If a user successfully signs in, they are automatically redirected to the page specified here") never fires.
The user does obtain a valid session (confirmed via Supabase.instance.client.auth.currentUser / a valid token after a custom OTP verification flow), but the app never navigates away from the current page on its own.
I confirmed this is specifically tied to the Custom Nav Bar Component: when I switch the exact same page's Nav Bar Style back to the default/built-in FlutterFlow Nav Bar (no other change to the auth flow), the automatic redirect to the Logged In Page works correctly and fires as expected on sign-in.
Expected Behavior
The automatic redirect to the "Logged In Page" should fire on successful sign-in regardless of which Nav Bar Style (built-in vs. Custom Nav Bar Component) is used on that page, consistent with the documented behavior.
Steps to Reproduce
- Create a project with Supabase Auth enabled.
- Create at least two pages, add both to a Custom Nav Bar Component (with selectedIndex and onItemTapped params, as required by FlutterFlow's Custom Nav Bar feature).
- Set one of these pages as the "Logged In Page" in Settings & Integrations > General > Initial Page.
- Set the Nav Bar Style of that page to "Custom Nav Bar Component".
- Sign in a user (I'm using a custom email OTP flow via Supabase.instance.client.auth.verifyOTP, which does result in a valid session/token).
- Observe: no automatic navigation happens to the Logged In Page.
- Now change the Nav Bar Style of that same page back to the default/built-in FlutterFlow Nav Bar (keep everything else identical) and repeat step 5.
- Observe: the automatic redirect now works correctly.
Reproducible from Blank
Bug Report Code (Required)
IT4szPHq7Y9NobhK+Kr+bsBB/GIWNk99aIIwscp/bxIgGIDzPOw+ZPWkN1dvTbTiT3w7IESmmkAepc7ekvPPVvAoBwyVc4Rq+JZxWBbwLDujUZOBErieP3d6AZ9RCEiHyrWFnxV7CPVeR1YT2GeEGdiWaHPaH4zxIlFISq/LZO4=
Visual documentation
Environment
- FlutterFlow version: 3.38.6
- Platform: Mobile (Flutterflow in Browser mode)
- Browser name and version: Google 152.0.7977.82
- Operating system and version affected: Windows 11
Additional Information
I confirmed via a manual test that context.goNamed(...) navigation to that page works fine from other pages — so the page itself and its route are functioning correctly. The issue is specifically that FlutterFlow's own internal sign-in-redirect mechanism does not trigger when Custom Nav Bar Component is used.
As a workaround, I'm currently forced to manually call context.goNamed(...) after a successful sign-in, which then creates other issues (e.g. race conditions with the page's own On Page Load logic and with the nav bar's internal isRouteVisible/rootModel logic in the generated navbar_model.dart, causing Looking up a deactivated widget's ancestor is unsafe errors in some cases).
Can we access your project?
Current Behavior
When a page configured as the "Logged In Page" (Settings & Integrations > General > Initial Page) uses a Custom Nav Bar Component as its Nav Bar Style, the automatic redirect on successful sign-in described in the documentation ("If a user successfully signs in, they are automatically redirected to the page specified here") never fires.
The user does obtain a valid session (confirmed via Supabase.instance.client.auth.currentUser / a valid token after a custom OTP verification flow), but the app never navigates away from the current page on its own.
I confirmed this is specifically tied to the Custom Nav Bar Component: when I switch the exact same page's Nav Bar Style back to the default/built-in FlutterFlow Nav Bar (no other change to the auth flow), the automatic redirect to the Logged In Page works correctly and fires as expected on sign-in.
Expected Behavior
The automatic redirect to the "Logged In Page" should fire on successful sign-in regardless of which Nav Bar Style (built-in vs. Custom Nav Bar Component) is used on that page, consistent with the documented behavior.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT4szPHq7Y9NobhK+Kr+bsBB/GIWNk99aIIwscp/bxIgGIDzPOw+ZPWkN1dvTbTiT3w7IESmmkAepc7ekvPPVvAoBwyVc4Rq+JZxWBbwLDujUZOBErieP3d6AZ9RCEiHyrWFnxV7CPVeR1YT2GeEGdiWaHPaH4zxIlFISq/LZO4=
Visual documentation
Environment
Additional Information
I confirmed via a manual test that context.goNamed(...) navigation to that page works fine from other pages — so the page itself and its route are functioning correctly. The issue is specifically that FlutterFlow's own internal sign-in-redirect mechanism does not trigger when Custom Nav Bar Component is used.
As a workaround, I'm currently forced to manually call context.goNamed(...) after a successful sign-in, which then creates other issues (e.g. race conditions with the page's own On Page Load logic and with the nav bar's internal isRouteVisible/rootModel logic in the generated navbar_model.dart, causing Looking up a deactivated widget's ancestor is unsafe errors in some cases).