Have something to say?

Tell us how we could make the product more useful to you.

Google Drive blocked β€” "This app is blocked" when trying to connect

Hi! I'm trying to connect Google Drive to my Superagent on Base44, but when I click "Connect" and get redirected to Google's authentication page, I receive the following error: "This app is blocked β€” This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked access." I tried both on mobile and desktop, across different browsers, and the error persists. All other Google integrations (Gmail, Calendar, Docs, Sheets, Tasks, and Meet) connected successfully β€” the issue is specific to Google Drive. I tried both on mobile and desktop, across different browsers, and the error persists. All other Google integrations (Gmail, Calendar, Docs, Sheets, Tasks, and Meet) connected successfully β€” the issue is specific to Google Drive. Thank you!

Jean Gomes 13 days ago

2

Greater Backend Control + Native Supabase Support for Production SaaS

We’ve been building a production SaaS platform on Base44 and overall the speed of development has been excellent. However, as we move closer to real-world deployment with multiple companies using the system, we’re encountering a few structural limitations that would benefit from deeper backend control. Key areas where additional functionality would significantly improve the platform: 1. Native Supabase Integration (Highly Needed for SaaS) For multi-tenant SaaS applications, Supabase provides mature features such as: Row Level Security (RLS) Auth management Database control Edge functions Direct support would allow developers to manage multi-company environments more reliably and securely. 2. Greater Backend Logic Control Currently many workflows rely on frontend-driven logic. In production SaaS systems we often need: Server-side functions Custom backend workflows Event-based triggers Validation that runs independently from the UI This helps ensure the system behaves correctly regardless of how the frontend is used. 3. Stronger Multi-Tenant Architecture Tools For SaaS platforms where multiple companies use the same application, developers need clearer control for: Company-level data isolation Authentication flows for new company owners vs invited team members RLS policies tied to company IDs Preventing cross-company data visibility 4. Auth Flow Flexibility Currently sign-up and access request flows are somewhat restrictive. It would help to allow: Custom onboarding flows Company creation during signup Admin approval logic customization Better handling of owner vs invited users Why this matters Base44 is extremely powerful for rapidly building SaaS products. With stronger backend and database control, it could also support more production-grade, enterprise SaaS systems, especially those using multi-tenant architectures. Would love to hear how others building SaaS on Base44 are handling these challenges as well. Thanks to the Base44 team for continuing to improve the platform.

aquo sync about 1 month ago

Fundamental issues using Base44 as a non-coder app builder

My First weeks experiences of using Base44 as a no-code user Feature Request Executive Summary I began using the platform on a Builder subscription, but within the first day I needed to upgrade to Pro, and shortly afterwards to the Elite plan, in order to continue developing my application. Within my first week, I have now exhausted approximately 95% of my monthly message credits. This has not been due to building new functionality, but primarily due to repeatedly fixing regressions introduced by the platform’s AI development agent. As a result, I now have no option but to stop development for the next three weeks until the subscription renews, because there is currently no way to purchase additional credits. The core issue appears to be a lack of safeguards in how the AI development agent operates. It can make changes without assessing the impact on existing functionality, without preventing previously working features from breaking, and without providing a reliable way to roll back to a stable version. This has created a development cycle where previously resolved issues reappear and must be corrected again, consuming credits each time. Based on my experience, this appears to be a structural limitation in the current development workflow rather than a one-off issue. Key Issues Encountered 1. AI Development Agent Creating Regression Loops During development, the in-app AI development agent repeatedly introduced bugs into parts of the application that had previously been working correctly. Even when the agent acknowledged the mistake and corrected it, similar issues would often reappear in later changes. At present there appears to be no mechanism to: Evaluate the impact of a change before it is applied Protect existing working functionality Reliably restore a known working version Without these safeguards, development can easily fall into a regression loop, where the same problems repeatedly return and require additional prompts to resolve. Each iteration consumes credits and slows development progress. 2. Credit Consumption Caused by Platform Behavior Because these regressions required repeated investigation and correction, the majority of my credits were consumed debugging issues introduced by the agent itself, rather than building new features. Currently there appears to be no way for users to: Stop an agent caught in a regression cycle Recover credits spent resolving platform-introduced problems Purchase additional credits during the current billing cycle The platform interface also displays a β€œPurchase more credits →” prompt when credits are exhausted, even though purchasing additional credits is not currently available. This creates a confusing user experience and suggests functionality that does not actually exist. 3. Reliability of Basic Data Operations Interestingly, some of the more advanced AI enrichment features worked extremely well and delivered fast, useful results. However, the most basic data operations proved unreliable. In particular: File imports sometimes required multiple attempts to complete successfully Database updates were inconsistent Long-running background tasks did not appear to complete or fail cleanly The job queue system did not appear to provide clear retry, timeout, or failure behavior These types of operations are generally well understood in software engineering, so their instability creates a significant reliability concern for anyone trying to build a production-quality application. 4. Absence of a Structured Change Management Approach From my perspective, many of these issues stem from the absence of a structured framework governing how the AI agent performs changes to an application. I believe both the AI agents and the Base44 organisation would benefit from implementing a recognized service management framework such as ITIL (other frameworks are available). Even a lightweight approach covering Incident Management, Problem Management, and Change Management could significantly reduce the types of issues described here. For example, the current process appears to lack: Impact assessment before applying changes Safeguards to prevent modifications during active incidents Reliable rollback capability Clear change tracking showing what was modified and when Without these controls, the AI agent effectively has unrestricted ability to modify application behavior without the safeguards typically present in modern development environments. 5. Expectations Placed on Non-Technical Users Another difficulty I encountered is that, although the platform is presented as a no-code solution, I have repeatedly been asked to perform tasks that are typically the responsibility of technical specialists. This has included being asked to: Investigate code-level issues Diagnose system behavior Identify technical faults Provide detailed explanations of what may be happening internally In practice, this places the user in the role of developer, systems analyst, and technical investigator, which is very different from the expectation created by the platform’s messaging that coding knowledge is not required. Overall Impact Area Impact Credits Approximately 95% consumed within the first week Development Work on the application has effectively halted Time Significant time spent repeatedly fixing the same issues Progress Development must pause until the next subscription cycle What I Am Not Asking For Sympathy or reassurance Temporary workarounds General assurances that the issue will not happen again What I Am Asking For Credit restoration Credits that were consumed fixing agent-introduced regressions should be restored. Migration support Assistance moving the project to a clean environment without consuming additional credits. Platform acknowledgement Confirmation that the regression loop and reliability issues described above are recognized and being addressed. User interface correction The β€œPurchase credits” prompt should not be shown if additional credits cannot actually be purchased. Closing Note I have invested a considerable amount of time working through these issues and reporting them constructively. My intention in posting this is not simply to complain, but to highlight platform-level reliability concerns that may affect other users building applications on the platform. The platform clearly has significant potential. However, improving reliability safeguards, development controls, and support structures would greatly improve the experience for users trying to build real applications.

Chip about 1 month ago

SN_ECOM

Agis comme un ingΓ©nieur logiciel senior et un expert e-commerce international. CrΓ©e un site web e-commerce moderne, professionnel et 100 % fonctionnel nommΓ© "KAMS.MSK STORE". EXIGENCES GΓ‰NΓ‰RALES : Site web + application installable (PWA) Design moderne, rapide, responsive (mobile, tablette, PC) Multilingue automatique : FranΓ§ais, Anglais, Espagnol, Russe, Chinois DΓ©tection automatique de la langue du visiteur Mode clair + mode sombre automatique SEO mondial optimisΓ© FONCTIONNALITΓ‰S E-COMMERCE : Produits dynamiques (images HD, prix, stock, catΓ©gories) Panier intelligent Commandes avec statut : en attente, payΓ©, livrΓ©, annulΓ© Historique client complet CoordonnΓ©es clients complΓ¨tes (nom, email, tΓ©lΓ©phone, pays) PAIEMENTS (prΓ©voir les espaces API) : Carte bancaire (Stripe) PayPal Business Wave Orange Money Djamo CinetPay Google Pay Apple Pay TABLEAU DE BORD ADMIN : Connexion admin sΓ©curisΓ©e Statistiques par jour / semaine / mois Graphiques de ventes Tendances par pays (USA, Chine, Russie, SΓ©nΓ©gal, Afrique, Monde) Suivi commandes et livraisons Gestion produits Gestion clients Notifications en temps rΓ©el (nouvelle commande) AUTRES : Bouton WhatsApp dynamique (numΓ©ro modifiable) Emplacement pour logo personnalisable Emails modifiables Code propre, structurΓ© et commentΓ© PrΓͺt pour dΓ©ploiement sur Vercel / Netlify Base de donnΓ©es (Supabase ou Γ©quivalent) Donne : Structure du projet Code frontend Code backend Base de donnΓ©es Instructions d’activation

Mamadou about 2 months ago

3