Request for native authentication support on iOS and Android

Dear Base44 Support Team,

We are experiencing an authentication issue when our app is running natively on iOS and Android devices.

In the web environment, authentication works as expected. However, in the native mobile app, when using social login methods such as Google OAuth or Apple Sign In, the current flow opens an external browser for the user to authenticate. That part is expected.

The problem happens after the user successfully authenticates: instead of returning control to the native app and closing the browser, the flow remains inside the browser and loads the app there. In other words, the user signs in successfully, but the session is completed in the browser rather than in the native app installed on the device.

This behavior breaks the user experience and prevents authentication from functioning as a truly native flow on iOS and Android.

We need Base44 to provide proper support for returning authentication to the native app using a mobile-compatible mechanism, such as:

• custom URL schemes;

• Universal Links on iOS;

• Android App Links on Android;

• or another official equivalent approach that allows OAuth / Apple Auth to complete inside the native app.

Based on the behavior we are observing, the callback appears to be returning to a web URL rather than to a native app redirect. As a result, the browser does not hand the flow back to the app.

We would appreciate it if you could provide:

1. Official guidance on how to configure Base44 authentication to work natively in iOS and Android apps;

2. Confirmation on whether there is currently official support for deep links, app links, or universal links in the authentication flow;

3. If this is not yet supported, we ask that this capability be treated as a product priority, since it is essential for serious use of social authentication in production mobile apps distributed through app stores.

Our goal is that after signing in with Google or Apple, the browser completes authentication, redirects properly to the installed native app, closes, and keeps the session active inside the app.

We look forward to your technical guidance and, if possible, a roadmap or official workaround for enabling this flow.

Best regards,