Skip to main content
Authentication lets users sign in to your app using accounts they already have—like Google, GitHub, or Apple ID. Bloom handles the complex security setup automatically, so you can add sign-in to your app without writing code or managing credentials yourself.

​
Why authentication matters

Authentication is essential for apps that:
  • Store user-specific data (profiles, preferences, saved content)
  • Need to know who’s using the app (personalized experiences)
  • Require secure access control (private content, paid features)
  • Track user activity or progress over time
With Bloom, authentication is pre-configured and ready to use. You don’t need to set up servers, manage API credentials, or worry about security best practices—it’s all handled automatically.

​
How authentication works in Bloom

Bloom uses OAuth, an industry-standard protocol that lets users sign in using existing accounts from trusted providers (Google, GitHub, Apple, etc.). When a user signs in:
  1. They tap “Sign in with Google” (or another provider) in your app
  2. They’re redirected to that provider’s secure login page
  3. They approve giving your app access to basic info (name, email)
  4. They’re returned to your app, now signed in
  5. Your app can now store and retrieve their personal data
Users never share their password with your app—OAuth keeps credentials secure.

​
Bloom-managed vs. custom credentials

Bloom offers two ways to configure authentication:

​
Available providers

Google

Status: Bloom-managed by default (ready to use immediately) Google authentication is pre-configured with Bloom-managed credentials. The toggle is on by default, meaning users can sign in with Google accounts right away.To use Bloom-managed Google auth:
  • The toggle stays on (green)
  • No additional configuration needed
  • Works immediately in your app
To use your own Google OAuth:
  1. Create a project in Google Cloud Console
  2. Enable the Google+ API
  3. Create OAuth 2.0 credentials
  4. Add your Authorized Origin to allowed origins
  5. Toggle off Bloom-managed and add your credentials in Bloom

Google OAuth Setup Guide

Learn how to create Google OAuth credentials
Status: Not configured by default GitHub authentication requires setup before it can be used.To add GitHub authentication:
1

Click 'Add with agent'

This opens a prompt where you can ask Bloom’s AI to set up GitHub OAuth for you.
2

Describe what you need

Example: “Add GitHub OAuth so users can sign in with their GitHub accounts”
3

Follow the setup instructions

Bloom will guide you through:
  • Creating a GitHub OAuth App
  • Configuring credentials
  • Testing the integration
GitHub OAuth requires creating an OAuth App in GitHub Developer Settings. You’ll need your Authorized Origin URL from Bloom.
Status: Not configured by default Apple Sign-In is required if you publish to the iOS App Store and offer other social login options.To add Apple authentication:
1

Click 'Add with agent'

Bloom’s AI assistant will help configure Apple Sign-In.
2

Enroll in Apple Developer Program

Apple Sign-In requires an Apple Developer Account ($99/year).
3

Create a Sign in with Apple service

Configure the service in Apple Developer Console.
4

Add credentials to Bloom

Follow Bloom’s prompts to enter your Apple Service ID and Key.
App Store requirement: If your iOS app offers Google or GitHub login, Apple requires you to also offer “Sign in with Apple” as an option.

Apple Sign-In Documentation

Learn about Sign in with Apple requirements

​
Testing authentication

After configuring providers, test that sign-in works:
1

Open your app preview

Use Bloom’s Live Preview or share your app to a test device.
2

Try signing in

Tap each configured provider’s sign-in button in your app.
3

Verify the flow

  • You should be redirected to the provider’s login page
  • After approving, you should return to your app signed in
  • Your app should have access to your basic profile info
4

Check logs if issues occur

If sign-in fails, check Logs for authentication errors. Common issues:
  • Incorrect Authorized Origin
  • Missing OAuth credentials
  • Provider-specific configuration errors

​
Switching between Bloom-managed and custom

You can switch authentication modes anytime:
  1. Toggle off the Bloom-managed switch for the provider
  2. Click to add your own OAuth credentials
  3. Paste your Client ID and Client Secret from the provider
  4. Save and test the integration
Your app will continue working during the switch—authentication doesn’t go down.

​
Common authentication questions

No! You only need to configure the providers you want your users to be able to use. Most apps start with just Google (which is pre-configured).
Yes. Start with one provider and add more anytime. Users who signed in with existing providers won’t be affected.
Bloom currently focuses on OAuth providers because they’re more secure and easier to maintain. If you need password auth, reach out to support or use custom authentication after exporting your code.
Yes! Bloom-managed credentials work in production apps. If you’re publishing to app stores, you may want to switch to custom credentials for full control and branding.
Authentication errors appear in Logs with detailed messages. Common issues:
  • Authorized Origin mismatch
  • Invalid or expired credentials
  • User denied permission
Check logs for specific error messages and solutions.

​
Troubleshooting

Authorization failed

Check:
  • Authorized Origin is correctly configured in provider dashboard
  • OAuth credentials are valid and not expired
  • Provider’s OAuth app is enabled and approved

Redirect loop

Check:
  • Redirect URI matches your Authorized Origin exactly
  • No trailing slashes or protocol mismatches
  • OAuth app settings saved correctly

User info not available

Check:
  • Required OAuth scopes are enabled (email, profile)
  • User approved data sharing during sign-in
  • Provider account has necessary information filled out

Bloom-managed not working

Check:
  • Toggle is enabled (green)
  • Click Refresh to reload provider status
  • Check Logs for system errors

Still having issues?

Check Logs for detailed error messages or contact Bloom support with your authentication configuration.

​
What’s next?

API Connections

Connect external services and APIs to your app

View Logs

Monitor authentication attempts and debug issues

Backend Dashboard

See user data and authentication metrics

Deploy your app

Share your app with users or publish to app stores