Could you please provide the method you're using to connect to Auth0 and "normally" redirect to your home page? That'll give me a clearer picture of what's going on.

In the meantime, let's try a few things based on my best guess for your problem!

Navigation Approaches

If you're using Flutter's basic Navigator, try this for handling the callback and redirecting:

// After successful authentication and getting your Auth0 callback
void handleAuthCallback(BuildContext context) async {
  // ... process Auth0 response to get user data/tokens ...

  // Ensure the widget is still mounted before navigating
  if (!context.mounted) return;

  // Use pushReplacement to prevent going back to the login screen
  Navigator.of(context).pushReplacement(
    MaterialPageRoute(builder: (context) => const HomePage()),
  );
}

Authentication and Asynchronous Handling

Are you successfully connecting to your database and authenticating correctly with Auth0? Double-check your Auth0 logs or any server-side logs if you have them.

Also, make sure you're awaiting all asynchronous calls! I sometimes forget to add await too, and it can definitely lead to unexpected navigation issues or state problems. 😅

Dynamic Authentication Listener

A robust way to handle authentication state and navigation is by using a StreamBuilder that dynamically listens to your authentication status. This approach automatically re-renders the UI based on whether the user is logged in or out.

For example:

return StreamBuilder<User?>( // Or whatever your user/auth state type is
  stream: auth.authStateChanges(), // Replace 'auth.authStateChanges()' with your actual auth state stream
  builder: (context, snapshot) {
    // If there's data (meaning the user is logged in)
    if (snapshot.hasData && snapshot.data != null) {
      return const HomeScreen(); // Or your main app content
    }
    // If there's no data (user is not logged in)
    else {
      return const AuthScreen(); // Your login/authentication page
    }
  },
);

This setup ensures that your UI always reflects the current authentication status, which helps prevent flickering or incorrect redirects.

Let me know if any of these help, or if you can share more code for your authentication flow!