Firebase AI Logic and its client SDKs were formerly called "Vertex AI in Firebase". To better reflect our expanded services and features (for example, we now support the Gemini Developer API!), we renamed and repackaged our services into Firebase AI Logic.
To securely access Google's generative AI models directly from your mobile or web apps, you can now choose a "Gemini API" provider — either the long-available Vertex AI Gemini API or now the Gemini Developer API. This means that you now have the option to use the Gemini Developer API, which provides a no-cost tier with reasonable rate limits and quotas.
Overview of steps to migrate to the Firebase AI Logic SDKs
Step 1: Choose the best "Gemini API" provider for your app and use cases.
Step 2: Enable the required APIs.
Step 3: Update the library used in your app.
Step 4: Update the initialization in your app.
Step 5: Update your code depending on the features that you use.
Step 1: Choose the best "Gemini API" provider for your app
With this migration, you have a choice in "Gemini API" provider:
The old "Vertex AI in Firebase" SDKs could only use the Vertex AI Gemini API.
The new Firebase AI Logic SDKs let you choose which "Gemini API" provider you want to call directly from your mobile or web app – either the Gemini Developer API or the Vertex AI Gemini API.
Review the differences between using the two Gemini API providers, especially in terms of supported features, pricing, and rate limits. For just one example, the Gemini Developer API doesn't support providing files using Cloud Storage URLs, but it might be a good choice if you want to take advantage of its no-cost tier and reasonable quota.
Step 2: Enable the required APIs
Ensure that all required APIs are enabled in your Firebase project to use your chosen "Gemini API" provider.
Note that you can have both of API providers enabled in your project at the same time.
Sign into the Firebase console, and then select your Firebase project.
In the Firebase console, go to the Firebase AI Logic page.
Click Get started to launch a guided workflow that helps you set up the required APIs and resources for your project.
Select the "Gemini API" provider that you'd like to use with the Firebase AI Logic SDKs. You can always set up and use the other API provider later, if you'd like.
Gemini Developer API — billing optional (available on the no-cost Spark pricing plan)
The console's workflow will enable the required APIs and create a Gemini API key in your project.Vertex AI Gemini API — billing required (requires the pay-as-you-go Blaze pricing plan)
The console's workflow will enable the required APIs in your project.
Continue in this migration guide to update the library and initialization in your app.
Step 3: Update the library used in your app
Update your app's codebase to use the Firebase AI Logic library.
Swift
In Xcode, with your app project open, update your Firebase package to v11.13.0 or later using one of the following options:
Option 1: Update all packages: Navigate to File > Packages > Update to Latest Package Versions.
Option 2: Update Firebase individually: Navigate to the Firebase package in the section called Package Dependencies. Right-click on the Firebase package, and then select Update Package.
Make sure that the Firebase package now shows v11.13.0 or later. If it doesn't, verify that your specified Package Requirements allow updating to v11.13.0 or later.
Select your app's target in the Project Editor, and then navigate to the Frameworks, Libraries, and Embedded Content section.
Add the new library: Select the + button, and then add FirebaseAI from the Firebase package.
After you've finished migrating your app (see the remaining sections in this guide), make sure to remove the old library:
Select FirebaseVertexAI-Preview, and then press the — button.
Kotlin
In your module (app-level) Gradle file (usually
<project>/<app-module>/build.gradle.kts
or<project>/<app-module>/build.gradle
), replace old dependencies (as applicable) with the following.Note that it might be easier to migrate your app's codebase (see the remaining sections in this guide) before deleting the old dependency.
// BEFORE dependencies {
implementation("com.google.firebase:firebase-vertexai:16.0.0-betaXX")} // AFTER dependencies { // Import the BoM for the Firebase platform implementation(platform("com.google.firebase:firebase-bom:33.13.0")) // Add the dependency for the Firebase AI Logic library // When using the BoM, you don't specify versions in Firebase library dependencies implementation("com.google.firebase:firebase-ai") }Sync your Android project with Gradle files.
Note that if you choose to not use the Firebase Android BoM, then just add
the dependency for the firebase-ai
library and accept the latest version
that's suggested by Android Studio.
Java
In your module (app-level) Gradle file (usually
<project>/<app-module>/build.gradle.kts
or<project>/<app-module>/build.gradle
), replace old dependencies (as applicable) with the following.Note that it might be easier to migrate your app's codebase (see the remaining sections in this guide) before deleting the old dependency.
// BEFORE dependencies {
implementation("com.google.firebase:firebase-vertexai:16.0.0-betaXX")} // AFTER dependencies { // Import the BoM for the Firebase platform implementation(platform("com.google.firebase:firebase-bom:33.13.0")) // Add the dependency for the Firebase AI Logic library // When using the BoM, you don't specify versions in Firebase library dependencies implementation("com.google.firebase:firebase-ai") }Sync your Android project with Gradle files.
Note that if you choose to not use the Firebase Android BoM, then just add
the dependency for the firebase-ai
library and accept the latest version
that's suggested by Android Studio.
Web
Get the latest version of the Firebase JS SDK for Web using npm:
npm i firebase@latest
OR
yarn add firebase@latest
Wherever you've imported the library, update your import statements to use
firebase/ai
instead.Note that it might be easier to migrate your app's codebase (see the remaining sections in this guide) before deleting the old imports.
// BEFORE import { initializeApp } from "firebase/app";
import { getVertexAI, getGenerativeModel } from "firebase/vertexai-preview";// AFTER import { initializeApp } from "firebase/app"; import { getAI, getGenerativeModel } from "firebase/ai";
Dart
Update to the use the
firebase_ai
package in yourpubspec.yaml
file by running the following command from your Flutter project directory:flutter pub add firebase_ai
Rebuild your Flutter project:
flutter run
After you've finished migrating your app (see the remaining sections in this guide), make sure to delete the old package:
flutter pub remove firebase_vertexai
Unity
Support for Unity wasn't available from "Vertex AI in Firebase".
Learn how to get started with the Firebase AI Logic SDK for Unity.
Step 4: Update the initialization in your app
Click your Gemini API provider to view provider-specific content and code on this page. |
Update how you initialize the service for your chosen API provider and
create a GenerativeModel
instance.
Swift
import FirebaseAI
// Initialize the Gemini Developer API backend service
let ai = FirebaseAI.firebaseAI(backend: .googleAI())
// Create a `GenerativeModel` instance with a model that supports your use case
let model = ai.generativeModel(modelName: "gemini-2.0-flash")
Kotlin
// Initialize the Gemini Developer API backend service
// Create a `GenerativeModel` instance with a model that supports your use case
val model = Firebase.ai(backend = GenerativeBackend.googleAI())
.generativeModel("gemini-2.0-flash")
Java
// Initialize the Gemini Developer API backend service
// Create a `GenerativeModel` instance with a model that supports your use case
GenerativeModel ai = FirebaseAI.getInstance(GenerativeBackend.googleAI())
.generativeModel("gemini-2.0-flash");
// Use the GenerativeModelFutures Java compatibility layer which offers
// support for ListenableFuture and Publisher APIs
GenerativeModelFutures model = GenerativeModelFutures.from(ai);
Web
import { initializeApp } from "firebase/app";
import { getAI, getGenerativeModel, GoogleAIBackend } from "firebase/ai";
// TODO(developer) Replace the following with your app's Firebase configuration
// See: https://firebase.google.com/docs/web/learn-more#config-object
const firebaseConfig = {
// ...
};
// Initialize FirebaseApp
const firebaseApp = initializeApp(firebaseConfig);
// Initialize the Gemini Developer API backend service
const ai = getAI(firebaseApp, { backend: new GoogleAIBackend() });
// Create a `GenerativeModel` instance with a model that supports your use case
const model = getGenerativeModel(ai, { model: "gemini-2.0-flash" });
Dart
import 'package:firebase_ai/firebase_ai.dart';
import 'package:firebase_core/firebase_core.dart';
import 'firebase_options.dart';
// Initialize FirebaseApp
await Firebase.initializeApp(
options: DefaultFirebaseOptions.currentPlatform,
);
// Initialize the Gemini Developer API backend service
// Create a `GenerativeModel` instance with a model that supports your use case
final model =
FirebaseAI.googleAI().generativeModel(model: 'gemini-2.0-flash');
Unity
Support for Unity wasn't available from "Vertex AI in Firebase".
Learn how to get started with the Firebase AI Logic SDK for Unity.
Note that depending on the capability you're using, you might not always
create a GenerativeModel
instance.
- To access an Imagen model,
create an
ImagenModel
instance.
Step 5: Update your code depending on features that you use
This step describes changes that may be required depending on which features you use.
If you use Cloud Storage URLs and you swapped to use the Gemini Developer API in this migration, then you must update your multimodal requests to include files as inline data (or use YouTube URLs for videos).
Several changes were introduced for the GA versions of the "Vertex AI in Firebase" SDKs. These same changes are required to use the Firebase AI Logic SDKs. Review the following lists for any changes that you might need to make in your code to accommodate taking up the Firebase AI Logic SDK.
Required for all languages and platforms
Function calling
If you implemented this feature before GA, then you'll need to make updates to how you define your schema. We recommend reviewing the updated function calling guide to learn how to write your function declarations.Generating structured output (like JSON) using
responseSchema
If you implemented this feature before GA, then you'll need to make updates to how you define your schema. We recommend reviewing the new structured output guide to learn how to write JSON schemas.Timeout
- Changed the default timeout for requests to be 180 seconds.
Required based on platform or language
Swift
Enumerations
Replaced most
enum
types withstruct
s with static variables. This change allows more flexibility for evolving the API in a backward-compatible way. When usingswitch
statements, you must now include adefault:
case to cover unknown or unhandled values, including new values that are added to the SDK in the future.Renamed the
BlockThreshold
enumeration toHarmBlockThreshold
; this type is now astruct
.Removed
unknown
andunspecified
cases from the following enumerations (nowstruct
s):HarmCategory
,HarmBlockThreshold
,HarmProbability
,BlockReason
, andFinishReason
.Replaced the enumeration
ModelContent.Part
with a protocol namedPart
to allow new types to be added in a backward-compatible way. This change is described in greater detail in the Content parts section.
Content parts
Removed the
ThrowingPartsRepresentable
protocol, and simplified the initializers forModelContent
to avoid occasional compiler errors. Images that don't encode properly will still throw errors when being used ingenerateContent
.Replaced the
ModelContent.Part
cases with the followingstruct
types conforming to thePart
protocol:.text
toTextPart
.data
toInlineDataPart
.fileData
toFileDataPart
.functionCall
toFunctionCallPart
.functionResponse
toFunctionResponsePart
Harm category
- Changed the
HarmCategory
to no longer be nested in theSafetySetting
type. If you're referring to it asSafetySetting.HarmCategory
, that can be replaced withHarmCategory
.
- Changed the
Safety feedback
- Removed the
SafetyFeedback
type, since it wasn't used in any of the responses.
- Removed the
Citation metadata
- Renamed the
citationSources
property tocitations
inCitationMetadata
.
- Renamed the
Total billable characters
- Changed the
totalBillableCharacters
property inCountTokensResponse
to be optional to reflect situations where no characters are sent.
- Changed the
Candidate response
- Renamed
CandidateResponse
toCandidate
to match other platforms.
- Renamed
Generation configuration
- Changed the public properties of
GenerationConfig
tointernal
. They all remain configurable in the initializer.
- Changed the public properties of
Kotlin
Enumerations
Replaced
enum
classes andsealed
classes with regular classes. This change allows more flexibility for evolving the API in a backward compatible way.Renamed the
BlockThreshold
enumeration toHarmBlockThreshold
.Removed values from the following enumerations:
HarmBlockThreshold
,HarmProbability
,HarmSeverity
,BlockReason
, andFinishReason
.
Blob methods
- Renamed all methods that included
Blob
as part of their name to useInlineData
instead.
- Renamed all methods that included
Safety settings
- Changed the field
method
to be nullable.
- Changed the field
Duration class
- Removed all usages of Kotlin's
Duration
class, and replaced it withlong
. This change provides better interoperability with Java.
- Removed all usages of Kotlin's
Citation metadata
- Wrapped all the fields previously declared in
CitationMetadata
into a new class calledCitation
. Citations can be found in the list calledcitations
inCitationMetadata
. This change allows better alignment of types across platforms.
- Wrapped all the fields previously declared in
Count tokens
- Changed the field
totalBillableCharacters
to be nullable.
- Changed the field
Total billable characters
- Changed the
totalBillableCharacters
property inCountTokensResponse
to be optional to reflect situations where no characters are sent.
- Changed the
Instantiating a model
- Moved the
requestOptions
parameter to the end of the parameter list to align with other platforms.
- Moved the
Live API
Removed
UNSPECIFIED
value for enum classResponseModality
. Instead usenull
.Renamed
LiveGenerationConfig.setResponseModalities
toLiveGenerationConfig.setResponseModality
.Removed the
LiveContentResponse.Status
class, and instead have nested the status fields as properties ofLiveContentResponse
.Removed the
LiveContentResponse
class, and instead have provided subclasses ofLiveServerMessage
that match the responses from the model.Changed
LiveModelFutures.connect
to returnListenableFuture<LiveSessionFutures>
instead ofListenableFuture<LiveSession>
.
Java
Enumerations
Replaced
enum
classes andsealed
classes with regular classes. This change allows more flexibility for evolving the API in a backward compatible way.Renamed the
BlockThreshold
enumeration toHarmBlockThreshold
.Removed values from the following enumerations:
HarmBlockThreshold
,HarmProbability
,HarmSeverity
,BlockReason
, andFinishReason
.
Blob methods
- Renamed all methods that included
Blob
as part of their name to useInlineData
instead.
- Renamed all methods that included
Safety settings
- Changed the field
method
to be nullable.
- Changed the field
Duration class
- Removed all usages of Kotlin's
Duration
class, and replaced it withlong
. This change provides better interoperability with Java.
- Removed all usages of Kotlin's
Citation metadata
- Wrapped all the fields previously declared in
CitationMetadata
into a new class calledCitation
. Citations can be found in the list calledcitations
inCitationMetadata
. This change allows better alignment of types across platforms.
- Wrapped all the fields previously declared in
Count tokens
- Changed the field
totalBillableCharacters
to be nullable.
- Changed the field
Total billable characters
- Changed the
totalBillableCharacters
property inCountTokensResponse
to be optional to reflect situations where no characters are sent.
- Changed the
Instantiating a model
- Moved the
requestOptions
parameter to the end of the parameter list to align with other platforms.
- Moved the
Live API
Removed
UNSPECIFIED
value for enum classResponseModality
. Instead usenull
.Renamed
LiveGenerationConfig.setResponseModalities
toLiveGenerationConfig.setResponseModality
.Removed the
LiveContentResponse.Status
class, and instead have nested the status fields as properties ofLiveContentResponse
.Removed the
LiveContentResponse
class, and instead have provided subclasses ofLiveServerMessage
that match the responses from the model.Changed
LiveModelFutures.connect
to returnListenableFuture<LiveSessionFutures>
instead ofListenableFuture<LiveSession>
.
Changed various Java builder methods to now correctly return the instance of their class, instead of
void
.
Web
Enumerations
- Removed values from the following enumerations:
HarmCategory
,BlockThreshold
,HarmProbability
,HarmSeverity
,BlockReason
, andFinishReason
.
- Removed values from the following enumerations:
Block reason
- Changed
blockReason
inPromptFeedback
to be optional.
- Changed
Changes required only if you're starting to use the Gemini Developer API (instead of the Vertex AI Gemini API):
Safety settings
- Removed usages of the unsupported
SafetySetting.method
.
- Removed usages of the unsupported
Inline data
- Removed usages of the unsupported
InlineDataPart.videoMetadata
.
- Removed usages of the unsupported
Dart
Enumerations
- Removed values from the following enumerations:
HarmCategory
,HarmProbability
,BlockReason
, andFinishReason
.
- Removed values from the following enumerations:
Data part
- Renamed
DataPart
toInlineDataPart
, and thestatic
data
function toinlineData
to align with other platforms.
- Renamed
Request options
- Removed
RequestOptions
sincetimeout
wasn't functional. It will be re-added in the near future, but it will be moved to theGenerativeModel
type to match other platforms.
- Removed
Stop sequences
- Changed the
stopSequences
parameter inGenerationConfig
to be optional and to default tonull
instead of an empty array.
- Changed the
Citations
- Renamed the
citationSources
property tocitations
inCitationMetadata
. TheCitationSource
type was renamed toCitation
to match other platforms.
- Renamed the
Unnecessary public types, methods, and properties
- Removed the following types, methods, and properties which were
unintentionally exposed:
defaultTimeout
,CountTokensResponseFields
,parseCountTokensResponse
,parseEmbedContentResponse
,parseGenerateContentResponse
,parseContent
,BatchEmbedContentsResponse
,ContentEmbedding
,EmbedContentRequest
, andEmbedContentResponse
.
- Removed the following types, methods, and properties which were
unintentionally exposed:
Count tokens
- Removed extra fields from the
countTokens
function that are no longer necessary. Onlycontents
is needed.
- Removed extra fields from the
Instantiating a model
- Moved the
systemInstruction
parameter to the end of the parameter list to align with other platforms.
- Moved the
Embedding functionality
- Removed unsupported embedding functionality (
embedContent
andbatchEmbedContents
) from the model.
- Removed unsupported embedding functionality (
Unity
Support for Unity wasn't available from "Vertex AI in Firebase".
Learn how to get started with the Firebase AI Logic SDK for Unity.
Possible errors related to migrating
As you're migrating to use the GA version of Firebase AI Logic, you might encounter errors if you haven't completed all of the required changes as described in this migration guide.
403 Error: Requests to this API firebasevertexai.googleapis.com ... are blocked.
If you receive a 403 error that says
Requests to this API firebasevertexai.googleapis.com ... are blocked.
,
it usually means that the Firebase API key in your
Firebase configuration file or object doesn't have a required API in its
allowlist for the product that you're trying to use.
Make sure that the Firebase API key used by your app has all the required APIs included in the key's "API restrictions" allowlist. For Firebase AI Logic, your Firebase API key needs to have at minimum the Firebase AI Logic API in its allowlist. This API should have been automatically added to your API key's allowlist when you enabled the required APIs in the Firebase console.
You can view all your API keys in the APIs & Services > Credentials panel in the Google Cloud console.
Give feedback about your experience with Firebase AI Logic