iOS app Google OAuth consent prompt shows base44.com instead of custom domain

iOS app Google OAuth consent prompt shows base44.com instead of custom domain (even with Custom Google OAuth enabled)
Custom domain: (connected + live)
Google OAuth: Custom Google OAuth configured + verified/approved weeks ago

Problem

Inside the Base44-generated iOS app, when a user taps “Log in with Google”, iOS displays the system consent prompt:

“Socially Versed” wants to use base44.com to sign in. This allows the app and website to share information about you.

This is confusing/off-brand and reduces trust, because it looks like users are signing into Base44 instead of our domain.

What’s confusing / inconsistent

• Web version + Safari on iPhone: Works fine / branding appears correctly (no base44.com issue)

• Base44 iOS app build (WKWebView / in-app auth): iOS prompt shows base44.com consistently

Expected behavior

When Custom Google OAuth is enabled and verified AND a custom domain is connected, the iOS consent prompt should reference the custom domain (or the branded auth domain used for the OAuth flow), not base44.com.

If Apple requires showing a domain, it should be the domain that actually represents the app’s authentication origin (e.g., auth.<mydomain.com> or the connected domain), or Base44 should provide a supported method to control what iOS displays.

Steps to reproduce

1. Install/open Base44-generated iOS app build for this app

2. Go to login screen

3. Tap “Log in with Google”

4. Observe iOS permission prompt referencing base44.com

Impact

• Brand trust issue (users think Base44 is the service they’re logging into)

• Higher login drop-off risk

• Conflicts with white-label expectations on paid plans

Request / Proposed solution options

Please implement one of the following:

1. True white-label auth origin for mobile builds so the system prompt references the customer domain when Custom OAuth is enabled.

2. Support an auth proxy domain like auth.customdomain.com (CNAME/Cloudflare-backed) used specifically for OAuth in mobile builds.

3. Provide a Base44 mobile build setting that ensures the OAuth flow originates from the custom domain (or a branded subdomain) rather than base44.com.

4. If Apple restrictions force the display, provide official documentation + exact technical reason and a recommended best-practice workaround to reduce user confusion.

Acceptance criteria

• With Custom Google OAuth enabled + verified and custom domain connected:

  • iOS consent prompt does not show base44.com

  • It shows the custom domain (or a branded subdomain designated for auth)

• Behavior is consistent across:

  • iOS app build (WKWebView)

  • Safari/PWA

  • Web browser