Hi @Mahesh Nannaware ,

Usually the problem is the redirect URL in the Identity Provider. It must exactly match the redirect URL used by the mobile app. Even small differences can break the redirect.

For example:

outsystems://<Your-environment>/IdP/Callback

Check below points as well:

• The same URL is configured in the IdP

• The scheme matches the mobile app settings

• There are no small differences like extra slashes or wrong protocol.

iOS is strict about redirects, so small mismatches often cause this issue.

Hope this helps,

Regards,

Manish Jawla

Hi @Mahesh Nannaware m

For OutSystems Mobile + System Browser SSO, iOS requires one of these two mechanisms:

Option A: Custom URL Scheme (most common)

• Example: myapp://callback

Option B: Universal Links (recommended for production)

• Example: https://myapp.domain.com/auth/callback

If the IdP redirects to anything else, iOS will not hand control back to the app. 

Ensure the Redirect URI exactly matches what the mobile app expects.

Also validate in Service Center → Mobile App → Advanced (or plugin configuration): 

• Ensure the Callback URL / Redirect URI matches the IdP 
• Ensure System Browser is enabled intentionally (not mixed with InAppBrowser)

And do NOT rely on client‑side redirects:

• window.location.href
• OutSystems Navigation.Navigate
• JavaScript redirects

These will not work after System Browser auth on iOS.

Hope this helps.

Cheers,

Saugat