Urgent: Google OAuth 403: disallowed_useragent in Telegram Web App

Hi Base44 Team, We're facing a critical issue preventing user login in our Telegram Web App. When users attempt to authenticate via Google, they encounter a 403: disallowed_useragent error. This happens because Google blocks OAuth flows within embedded browsers (like Telegram's WebView) for security reasons. While we've attempted client-side workarounds (e.g., using Telegram.WebApp.openLink()), the core problem persists as the initial redirect to Google's authentication page is handled by the Base44 platform itself within the WebView, and the return flow isn't seamless for TWA. This is a significant blocker for user acquisition and experience in Telegram. Could you please provide guidance or a platform-level solution to correctly handle Google authentication within Telegram Web Apps, opening the OAuth flow in an external browser and ensuring a proper return? What is the current status of this issue, and when can we expect a fix or a recommended workaround? Thanks for your urgent attention to this.