# Silent login: Users redirected to login after mobile authentication

**URL:** <https://community.auth0.com/t/silent-login-users-redirected-to-login-after-mobile-authentication/192391>\
**Category:** Dev to Dev Hub\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [September 25, 2025, 8:37am UTC](https://community.auth0.com/t/silent-login-users-redirected-to-login-after-mobile-authentication/192391 "2025-09-25T08:37:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sudyaljyoti](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sudyaljyoti/32/74944_2.png) [@sudyaljyoti](https://community.auth0.com/u/sudyaljyoti)\
**Post date:** [September 25, 2025, 8:37am UTC](https://community.auth0.com/t/silent-login-users-redirected-to-login-after-mobile-authentication/192391/1 "2025-09-25T08:37:53Z")

</div>

I’m implementing `@auth0/auth0-react` and facing an authentication flow issue.

**Current Issue:** Users authenticate on our mobile app, then navigate to our web app, but get redirected to the login page instead of staying logged in.

**Expected Behavior:** Users should remain authenticated across both mobile and web platforms without needing to log in twice.

**What I’ve Tried:** I attempted using `getAccessTokenSilently()` to check for an active session, but this approach didn’t resolve the issue.

**Questions:**

1. How should I handle cross-platform authentication with `@auth0/auth0-react`?

2. Is there a recommended way to check for existing tokens/sessions in the web app?

3. Are there specific configuration settings I should consider for this scenario?

Any guidance or examples would be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![remus.ivan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/remus.ivan/32/68771_2.png) [@remus.ivan](https://community.auth0.com/u/remus.ivan)\
**Post date:** [September 30, 2025, 9:55pm UTC](https://community.auth0.com/t/silent-login-users-redirected-to-login-after-mobile-authentication/192391/2 "2025-09-30T21:55:44Z")

</div>

Hi @sudyaljyoti,

Welcome to the Auth0 Community!

The latest and most modern solution to this use case was recently made available in EA and is described in our [Native to Web SSO](https://auth0.com/docs/authenticate/single-sign-on/native-to-web) and [Configure and Implement Native to Web SSO](https://auth0.com/docs/authenticate/single-sign-on/native-to-web/configure-implement-native-to-web) documentation, which relies on a `session_transfer_token` , instead of a classic SSO cookie that might be blocked for various reasons due to browsers policies trying to prevent sharing third-party or cross-site cookies.

Thanks,

Remus
