CANCELLATION REDIRECT

When users cancel Apple login, they're redirected to Base44's platform OAuth callback endpoint (https://app.base44.com/api/apps/auth/apple/callback), not the customer’s app's domain. The platform is serving the raw JSON error directly on its own domain, so the customer app's code can never intercept it. Solutions: The key thing to understand here: This is the expected behaviour for Base44's built-in Apple login. The platform handles the OAuth callback and then redirects back to your app. The raw JSON error appears on

app.base44.com

suggests the platform is not cleanly redirecting the user back to your app's login page after a cancellation.

This is a platform-level behaviour that you cannot fix from your app's code. Since the cancellation redirect happens on Base44's domain before your app is involved, there's no way to intercept it client-side.

Your options are:

1. Accept the current behaviour — most users won't cancel Apple login, and the error is technically accurate (though not pretty).

2. Set up custom Apple OAuth — if you configure your own Apple OAuth credentials (available on the Elite plan), you control the

   redirect_uri

   and can point it to your own domain, giving you full control over cancellation handling.

3. Submit feedback — this is a valid platform-level UX issue. You can report it at feedback.base44.com so the team can improve the cancellation redirect behaviour.