# Login\_hint on swift not working with saml idp **URL:** \ **Category:** Get Help\ **Tags:** login-experience, new-universal-login-experience\ **Created:** [April 1, 2025, 4:56pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871 "2025-04-01T16:56:55Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ben30](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ben30/32/73295_2.png) [@ben30](https://community.auth0.com/u/ben30)\ **Post date:** [April 1, 2025, 4:56pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/1 "2025-04-01T16:56:55Z")
Hi all, We’ve been using login\_hint in our Swift iOS app for the past month or two without any issues. When a user logs in via SAML (Okta), we capture and store their email. On subsequent logins, we pre-populate the login\_hint parameter with that email, and until recently, this reliably redirected them to Okta as expected. However, recently (unknown time start - est last day or two), this behavior changed. Now, when we pass the login\_hint with the SAML email, the user is incorrectly sent to the universal login’s username/password screen instead of being redirected to Okta. If the user taps “Back” and then goes through the regular login flow manually, everything works correctly—they enter their email and are routed to Okta as expected. Nothing has changed on our end as far as we know. Has there been a recent update to how login\_hint is handled, or is there something else we should be looking into? Appreciate any insights or guidance. Thanks! ---
**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\ **Post date:** [April 1, 2025, 8:02pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/3 "2025-04-01T20:02:23Z")
Hi @ben30, Thanks for your question. As far as I know, there haven’t been any recent updates to how the `login_hint` is handled or to the Auth0 Swift SDK. I just tested this flow on my end by going to my `/authorize` endpoint in the browser, and I got the `login_hint` parameter to populate the email field as expected using a SAML connection. Just to clarify, are you also specifying the `connection` query parameter in your request? If not, it might help to include both `connection` and `login_hint` query parameters to send the user to log in using their SAML credentials. Thanks, Rueben ---
**Author:** ![ben30](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ben30/32/73295_2.png) [@ben30](https://community.auth0.com/u/ben30)\ **Post date:** [April 2, 2025, 1:41pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/4 "2025-04-02T13:41:09Z")
I am not specifying the connection, but up until recently it worked fine with no issues, so I don’t know why it wouldn’t work? Ben ---
**Author:** ![ben30](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ben30/32/73295_2.png) [@ben30](https://community.auth0.com/u/ben30)\ **Post date:** [April 2, 2025, 1:45pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/5 "2025-04-02T13:45:34Z")
What’s weird is that the login hint goes straight to the U/P flow, so the login hint is populating ---
**Author:** ![ben30](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ben30/32/73295_2.png) [@ben30](https://community.auth0.com/u/ben30)\ **Post date:** [April 2, 2025, 1:46pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/6 "2025-04-02T13:46:25Z")
Alternatively, is there a way to just prefill the email box? so the user still has to click continue? ---
**Author:** ![ben30](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ben30/32/73295_2.png) [@ben30](https://community.auth0.com/u/ben30)\ **Post date:** [April 2, 2025, 3:19pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/7 "2025-04-02T15:19:09Z")
I have tried restoring an old version of the application in which the flow used to workand this flow still doesn’t work, so it must be something on the server side ---
**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\ **Post date:** [April 3, 2025, 11:51pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/8 "2025-04-03T23:51:39Z")
Hi @ben30, Thanks for the update. Yes, if a `connection` parameter is not specified, it will redirect to the U/P flow. On that page, if the `login_hint` is passed and the SAML connection is displayed as a button, the user can click that button, and the email address will populate downstream. Can you see if the `login_hint` works in a regular browser? ---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [April 24, 2025, 7:23pm UTC](https://community.auth0.com/t/login-hint-on-swift-not-working-with-saml-idp/184871/9 "2025-04-24T19:23:39Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.