Help me, i have problem with publication

Ask for Help
1

I’m experiencing a Forbidden error during sign-in, especially inside Telegram WebView (Telegram Mini App). I’ve tried the common fixes, but nothing has worked so far.

Project info

Goal
Reliable user authentication inside Telegram WebView and stable access to the published app (no Forbidden).

Current access settings

  • Settings → Access → Sign-in: Public with email
  • Who can sign in: All emails can sign in
  • Settings → User data: Collect real user email addresses = ON, Always set user authentication cookie = ON
  • Users table is set as User Profiles; email column type = Email; role stored in role (text/choice).
  • Moderator/owner profile exists (role = moderator).

Reproduction steps

  1. Open the published app inside Telegram WebView (via bot/button).
  2. Tap Sign in with Google → complete OAuth.
  3. After the redirect, I get Forbidden.
  4. Opening the same link in an external browser (Chrome/Safari): Google sign-in usually succeeds.
  5. Tried email (PIN) sign-in as well — some users still hit Forbidden/authorization error after the PIN step (intermittent).
  6. I tested toggling Who can sign in (All emails / Users table), cleared cache/cookies, switched Collect real emails and Always set user authentication cookie on/off — the issue persists.

Expected behavior
Sign-in (Google or email PIN) completes successfully and grants access, including inside Telegram WebView.

Actual behavior
Inside Telegram WebView I receive Forbidden after the final auth redirect; occasionally similar behavior occurs with email PIN.

Additional context

  • Data source: Glide Tables.
  • The app is published; the error occurs specifically at authentication.
  • If there are known limitations with Google OAuth in embedded WebViews, please confirm and advise the recommended auth method for Telegram Mini App (e.g., force external browser, rely solely on email PIN, etc.).

Happy to provide

  • Timestamps of recent attempts (UTC+2 / Europe/Warsaw)
  • Screenshots of Settings → Access / User data
  • HAR/Network logs of the auth redirects
  • Test account / workspace invite

Thanks in advance for your help troubleshooting and for guidance on the correct setup for Telegram WebView.

1 Like
2

This is the problematic part. It has been there since the beginning of Glide when people try to sign in from a pseudo browser (e.g a link from Facebook, Instagram etc).

Unfortunately it seems Glide can not do anything in this case.