# Firebase console

A console for managing Firebase products, apps, and project-level settings.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Firebase Phone Number Authentication in Kotlin/Wasm (Part 3)

DevFeed: [Firebase Phone Number Authentication in Kotlin/Wasm (Part 3)](<https://devfeed.tech/articles/firebase-phone-number-authentication-in-kotlin-wasm-part-3-55442.md>)

Original publisher: [Read original article](<https://proandroiddev.com/kotlin-wasm-auth-part-3-phone-sign-in-9b47f1993940?source=rss----c72404660798---4>)

Author: Tomislav Mladenov

Published: 2026-09-19T16:03:23Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Firebase console](<https://devfeed.tech/topics/firebase-console.md>), [Wasm components](<https://devfeed.tech/topics/wasm-components.md>)

Tags: [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [billing](<https://devfeed.tech/tags/billing.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [firebase-console](<https://devfeed.tech/tags/firebase-console.md>), [firebaseauthentication](<https://devfeed.tech/tags/firebaseauthentication.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [kotlin-wasm](<https://devfeed.tech/tags/kotlin-wasm.md>), [number](<https://devfeed.tech/tags/number.md>), [phone](<https://devfeed.tech/tags/phone.md>), [phone-authentication](<https://devfeed.tech/tags/phone-authentication.md>), [recaptcha](<https://devfeed.tech/tags/recaptcha.md>), [region](<https://devfeed.tech/tags/region.md>), [regions](<https://devfeed.tech/tags/regions.md>), [requires](<https://devfeed.tech/tags/requires.md>), [series](<https://devfeed.tech/tags/series.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [sms](<https://devfeed.tech/tags/sms.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Firebase phone sign-in in Kotlin/Wasm needs Blaze billing enabled and the desired SMS region allowed in Firebase settings; otherwise attempts fail with `auth/billing-not-enabled` or `auth/operation-not-allowed`. The flow adds bindings for `RecaptchaVerifier`, `PhoneAuthProvider` and `signInWithCredential`, plus a DOM element for the verifier. Each attempt should clear the previous verifier and create a fresh one because reCAPTCHA tokens are single-use; reusing one can cause retries to fail with `auth/invalid-app-credential`. Sign-in first verifies the phone number and stores its verification ID, then exchanges that ID and the SMS code for a credential and signed-in user. For development, a console-registered fictional number and fixed code can be used with app verification disabled, avoiding captcha, real SMS and quota use; the excerpt cautions against shipping with that switch enabled.

### Source excerpt

Part 3 of the Wasm series is phone sign-in, and the Kotlin code is once again the easy half. Before you write a line, know the three Firebase console traps. Phone auth now requires the Blaze plan, and until billing is on every attempt fails with auth/billing-not-enabled, fictional test numbers included. The SMS region policy (Authentication -> Settings -> SMS region policy) denies all regions by default and returns auth/operation-not-allowed until you allow yours. And reCAPTCHA tokens are single-use, which we'll get to in the code. Console sorted? Good, the Wasm part is pleasantly small. Phone sign-in needs four things our part 1 bindings didn't have: a reCAPTCHA verifier, the phone provider, a credential sign-in function and the user's phone number. All of them go into the same @file:JsModule("firebase/auth") file: external class RecaptchaVerifier( auth: Auth, container: String, parameters: JsAny, ) : JsAny { fun clear() } external class PhoneAuthProvider(auth: Auth) : JsAny { fun verifyPhoneNumber(phoneNumber: String, applicationVerifier: RecaptchaVerifier): Promise<JsString> companion object { fun credential(verificationId: String, verificationCode: String): JsAny } } external fun signInWithCredential(auth: Auth, credential: JsAny): Promise<UserCredential> Two small js() helpers stand in for what would be dynamic on Kotlin/JS: one builds the verifier options, the other flips Firebase's testing switch: private fun invisibleRecaptchaParams(): JsAny = js("({ size: 'invisible' })") private fun disableAppVerificationForTesting(auth: Auth): Unit = js("{ auth.settings.appVerificationDisabledForTesting = true; }") The verifier also wants a real DOM element to attach to, and our UI is a Compose canvas, so we create a plain div for it once: private fun recaptchaContainer(): String { if (document.getElementById(RECAPTCHA_CONTAINER_ID) == null) { val container = document.createElement("div") container.setAttribute("id", RECAPTCHA_CONTAINER_ID) document.body?.appendChild(cont

## Dynamic configuration in Java with Server-Side Firebase Remote Config

DevFeed: [Dynamic configuration in Java with Server-Side Firebase Remote Config](<https://devfeed.tech/articles/dynamic-configuration-in-java-with-server-side-firebase-remote-config-23887.md>)

Original publisher: [Read original article](<https://medium.com/firebase-developers/dynamic-configuration-in-java-using-server-side-firebase-remote-config-9d30a3c2e1a1?source=rss----8e8b7dc6774d---4>)

Author: Athira M

Published: 2025-10-24T06:33:20Z

Content type: tutorial

Language: en

Sources: [Firebase Developers](<https://devfeed.tech/sources/firebase-developers-medium.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [Java](<https://devfeed.tech/topics/java.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [feature flags](<https://devfeed.tech/topics/feature-flags.md>), [Firebase console](<https://devfeed.tech/topics/firebase-console.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [feature-flags](<https://devfeed.tech/tags/feature-flags.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [firebase-console](<https://devfeed.tech/tags/firebase-console.md>), [firebase-remote-config](<https://devfeed.tech/tags/firebase-remote-config.md>), [java](<https://devfeed.tech/tags/java.md>), [maven](<https://devfeed.tech/tags/maven.md>), [remote-config](<https://devfeed.tech/tags/remote-config.md>), [sdks](<https://devfeed.tech/tags/sdks.md>)

### AI overview

This tutorial explains how to use server-side Firebase Remote Config with Java to externalize backend configuration and feature flags. It describes how the Java server fetches the full configuration template, evaluates conditions locally through the SDK, initializes the Firebase Admin SDK, defines safe defaults, and evaluates parameters using runtime context.

### Source excerpt

Dynamic Configuration in JavaUsing Server-Side Firebase Remote Config Firebase Remote Config is a powerful, cloud-based service that lets you dynamically change your app's behavior and appearance without requiring users to update your app. It's been a game-changer for feature flags and dynamic theming on mobile and web platforms. But what about your backend, or your critical API or Java micro-service? The great news is that Firebase has expanded its support, bringing this powerful tool to the server side with SDKs for Node.js, Python, Go, and Java. This allows you to control server behavior and externalize configuration directly from the Firebase console. The key difference: where evaluation happens If you're familiar with client-side Remote Config, you know the client makes a request, and the Firebase service returns the final, evaluated configuration. The server-side model is fundamentally different: The Java server fetches the entire configuration template (parameters, values, and conditions) from the Remote Config service. The Java server then performs the condition evaluation locally, using the SDK. This shift means your server is in control, making local decisions based on attributes like user ID, location, or subscription tier. This is efficient and perfect for dynamic server logic. 🛠 Setting up Remote Config in Java Let's walk through how to integrate this into your backend, using a Payment Gateway Feature Flag as our running example. Step 1: Add the Firebase Admin SDK First, add the Firebase Admin SDK dependency to your project's configuration file (e.g., pom.xml for Maven). <dependency> <groupId>com.google.firebase</groupId> <artifactId>firebase-admin</artifactId> <version>9.7.0</version> </dependency>Step 2: Initialize the Admin SDK Your server needs secure access to Firebase. We'll use a Service Account to initialize the Admin SDK. import com.google.auth.oauth2.GoogleCredentials; import com.google.firebase.FirebaseApp; import com.google.firebase.Firebas

## Introducing Gemini in Firebase

DevFeed: [Introducing Gemini in Firebase](<https://devfeed.tech/articles/introducing-gemini-in-firebase-16546.md>)

Original publisher: [Read original article](<https://firebase.blog/posts/2024/05/gemini-in-firebase>)

Author: Thevi Sundaralingam; Richie Foreman; Viswanathan Munisamy

Published: 2024-05-27T00:00:00Z

Content type: article

Language: en

Sources: [Firebase Blog](<https://devfeed.tech/sources/firebase-blog.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [Firebase console](<https://devfeed.tech/topics/firebase-console.md>), [Crashlytics](<https://devfeed.tech/topics/crashlytics.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistance](<https://devfeed.tech/tags/ai-assistance.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [app-quality](<https://devfeed.tech/tags/app-quality.md>), [applications](<https://devfeed.tech/tags/applications.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud-storage](<https://devfeed.tech/tags/cloud-storage.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [console](<https://devfeed.tech/tags/console.md>), [crashlytics](<https://devfeed.tech/tags/crashlytics.md>), [dart](<https://devfeed.tech/tags/dart.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [developers](<https://devfeed.tech/tags/developers.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [firebase-app-check](<https://devfeed.tech/tags/firebase-app-check.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [generate](<https://devfeed.tech/tags/generate.md>), [google-i-o](<https://devfeed.tech/tags/google-i-o.md>), [ios](<https://devfeed.tech/tags/ios.md>), [launch](<https://devfeed.tech/tags/launch.md>), [vertex-ai](<https://devfeed.tech/tags/vertex-ai.md>)

### AI overview

Gemini in Firebase is an AI assistant in the Firebase console, built on a customized Gemini model trained with Firebase expertise. It answers product questions, generates code snippets, and offers troubleshooting support. Its Crashlytics integration can produce crash summaries, sample code, recommended next steps, and industry best practices to help developers triage issues. The source says it is built on Gemini for Google Cloud to support organization-wide adoption while meeting security, privacy, and compliance requirements. The excerpt lists example uses, including Firebase project questions, error explanations, App Check code, and a Cloud Storage upload snippet, but cuts off during the upload requirements.

### Source excerpt

AI Assistance for App Developers

## A Crash Course in Using the New Audiences in Analytics

DevFeed: [A Crash Course in Using the New Audiences in Analytics](<https://devfeed.tech/articles/a-crash-course-in-using-the-new-audiences-in-analytics-16303.md>)

Original publisher: [Read original article](<https://firebase.blog/posts/2019/01/a-crash-course-in-using-new-audiences>)

Author: Todd Kerpelman

Published: 2019-01-23T00:00:00Z

Content type: tutorial

Language: en

Sources: [Firebase Blog](<https://devfeed.tech/sources/firebase-blog.md>)

Topics: [Google Analytics](<https://devfeed.tech/topics/google-analytics.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>), [Firebase console](<https://devfeed.tech/topics/firebase-console.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud-messaging](<https://devfeed.tech/tags/cloud-messaging.md>), [dynamic-audiences](<https://devfeed.tech/tags/dynamic-audiences.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [google-analytics](<https://devfeed.tech/tags/google-analytics.md>), [remote-config](<https://devfeed.tech/tags/remote-config.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

This tutorial explains how audiences in Google Analytics for Firebase work, including the dynamic audience feature that lets users enter and leave audiences as they meet or stop meeting defined criteria. It also describes how audience conditions are evaluated across clients and the server.

### Source excerpt

News, tutorials, and updates from the Firebase team.

## Crash reporting in Firebase

DevFeed: [Crash reporting in Firebase](<https://devfeed.tech/articles/crash-reporting-in-firebase-25836.md>)

Original publisher: [Read original article](<https://segunfamisa.com/posts/firebase-crash-reporting>)

Author: Segun Famisa

Published: 2016-05-26T12:05:30Z

Content type: tutorial

Language: en

Sources: [Segun Famisa](<https://devfeed.tech/sources/segun-famisa.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [Android](<https://devfeed.tech/topics/android.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Firebase console](<https://devfeed.tech/topics/firebase-console.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [crash-reporting](<https://devfeed.tech/tags/crash-reporting.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [reporting](<https://devfeed.tech/tags/reporting.md>)

### AI overview

The excerpt describes a 2016 Android setup for Firebase Crash Reporting. It lists prerequisites: an Android device with Google Play services 9.0.0 or later, the Google Play services SDK, Android Studio 1.5 or later, and an Android project. Setup involves creating or importing a project in the Firebase console, registering the app's package name, placing google-services.json in the app module, and adding/configuring the SDK and Google services plugin. Once configured, Firebase automatically reports fatal unhandled exceptions without additional code; the excerpt also says handled non-fatal exceptions can be reported manually, but cuts off before explaining how.

### Source excerpt

Update: (21st of September, 2016) Since publication of this post, Firebase has changed and evolved, and this post has been updated to the new state of things. Last week, at Google I/O, Google announced a number of interesting new features in Firebase. The new Firebase is said to be a "Unified app platform for mobile developers" adding new tools to help develop faster, improve app quality, engage users and monetize apps. You can check out this intro video here. Some of the new features in the Firebase upgrade include: Firebase Analytics. Firebase Cloud Messaging. Firebase Test Lab and Crash Reporting. Firebase Notifications, Dynamic Links, App Indexing, AdWords, Firebase Invites etc I've been playing around the new product and it's been amazing. In this post, I'm going to show you how to use Firebase for Crash reporting in order to improve the quality of apps that you ship. How to use? The new Firebase works with the new Google Play Services 9.0, and to use it in Android Studio, you need to follow these steps: Setup Firebase 1. Pre-requisites Ensure your development environment meets the pre-requisite requirements. The Pre-requisites as seen here are: An Android device running Google Play services 9.0.0 or later The Google Play services SDK from the Android SDK Manager Android Studio 1.5 or higher An Android Studio project and its package name. 2. Add Firebase to your app Next step is to add Firebase to your app. To do this, you need to create a project on the Firebase console. Click on Create New Project (if you're starting a new project) or import Google Project if you're importing an existing project, and follow through the steps. Now, within your app, click on click on Add Firebase to your Android app. You'll be prompted to add your package name, and also to download a config file. This is the usual google-services.json file. Be sure to add it to your app module's directory. (e.g /app) 3. Add the SDK to your app To use Firebase in your app, you need to add and se