1241 results found

1. Allow the App Testing Agent to persist user state between test runs

   It would be great if the App Testing Agent could persist a user session or saved app state between test runs. This would allow tests to start from a predefined state instead of always going through the onboarding or login flow, making it much easier and faster to test authenticated features and later stages of the app.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App Distribution  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Shadrack

   import 'package:flutter/material.dart';
   import 'package:firebasecore/firebasecore.dart';

   // Import the firebaseappcheck plugin
   import 'package:firebaseappcheck/firebaseappcheck.dart';

   Future<void> main() async {
   WidgetsFlutterBinding.ensureInitialized();
   await Firebase.initializeApp();
   await FirebaseAppCheck.instance.activate(
   // You can also use a ReCaptchaEnterpriseProvider provider instance as an
   // argument for webProvider
   webProvider: ReCaptchaV3Provider('recaptcha-v3-site-key'),
   // Default provider for Android is the Play Integrity provider. You can use the "AndroidProvider" enum to choose
   // your preferred provider. Choose from:
   // 1. Debug provider
   // 2. Safety Net provider
   // 3. Play Integrity provider
   androidProvider: AndroidProvider.debug,
   // Default provider for iOS/macOS is the Device Check provider. You can use the "AppleProvider" enum to choose
   // your preferred provider. Choose from:
   // 1. Debug provider
   // 2. Device Check provider
   // 3. App Attest provider
   // 4. App Attest provider with fallback to Device Check provider (App Attest provider is only available on iOS 14.0+, macOS 14.0+)
   appleProvider: AppleProvider.appAttest,
   );
   runApp(App());
   }

   import 'package:flutter/material.dart';
   import 'package:firebasecore/firebasecore.dart';

   // Import the firebaseappcheck plugin
   import 'package:firebaseappcheck/firebaseappcheck.dart';

   Future<void> main() async {
   WidgetsFlutterBinding.ensureInitialized();
   await Firebase.initializeApp();
   await FirebaseAppCheck.instance.activate(
   // You can also use a ReCaptchaEnterpriseProvider provider instance as an
   // argument for webProvider
   webProvider: ReCaptchaV3Provider('recaptcha-v3-site-key'),
   // Default provider for Android is the Play Integrity provider. You can use the "AndroidProvider" enum to choose
   // your preferred provider. Choose from:
   // 1. Debug provider
   // 2. Safety Net provider
   // 3. Play Integrity provider
   androidProvider: AndroidProvider.debug,
   // Default provider for iOS/macOS is the Device Check provider. You can use the "AppleProvider"… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App Distribution  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Rap drill

   Des musiques social et spirituels pour motiver et faire réfléchir les gens
   Vidéo alléchantes

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Firebase AI Logic  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Feature Request: Support for Zstandard (zstd) Compression

   💡 Feature Proposal

   Is your feature request related to a problem? Please describe.
   Currently, Firebase Crashlytics (both the backend and the upload-symbols / Gradle tooling) strictly requires standard .zip (DEFLATE) archives for symbolication files like dSYMs and ProGuard mappings.

   For large-scale applications, dSYM files can easily grow to several gigabytes. Compressing them with standard single-threaded zip tools slows down CI/CD pipelines significantly, while multi-threaded tools or better algorithms cannot be fully utilized because the Firebase backend rejects anything other than standard ZIP files.

   Describe the solution you'd like
   We would like Firebase Crashlytics to natively support Zstandard (.zst or .tar.zst) compression for symbol files uploads (via Web Console, Fastlane, and CLI/Gradle plugins).

   Zstd provides a dramatically better compression/decompression speeds and ratios compared to DEFLATE (Gzip/Zip). Integrating it into the upload-symbols binary and Crashlytics backend would allow:
   1. Faster archiving stages on CI runners (saving expensive compute minutes).
   2. Smaller payload sizes, reducing network transit times when pushing symbols to Firebase.

   Describe alternatives you've considered
   - Using multi-threaded ZIP alternatives like pigz -K, which helps with CPU times but doesn't solve the compression ratio limits of the older DEFLATE algorithm.
   - Uncompressing .zst archives on intermediate CI stages just to feed raw directories into upload-symbols, which wastes disk I/O and runner storage.

   Additional context
   Many modern engineering pipelines and data lakes have already migrated to Zstd as their default compression standard. Bringing native Zstd support to Crashlytics symbol uploads would highly optimize modern mobile CI/CD workflows (especially for heavy enterprise iOS/Android apps).

   💡 Feature Proposal

   Is your feature request related to a problem? Please describe.
   Currently, Firebase Crashlytics (both the backend and the upload-symbols / Gradle tooling) strictly requires standard .zip (DEFLATE) archives for symbolication files like dSYMs and ProGuard mappings.

   For large-scale applications, dSYM files can easily grow to several gigabytes. Compressing them with standard single-threaded zip tools slows down CI/CD pipelines significantly, while multi-threaded tools or better algorithms cannot be fully utilized because the Firebase backend rejects anything other than standard ZIP files.

   Describe the solution you'd like
   We would like Firebase Crashlytics to natively support Zstandard (.zst or … more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Crashlytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Feature Request: Include Crashlytics issue notes in BigQuery Export

   Hi Firebase Team,

   I would like to submit a feature request regarding Firebase Crashlytics and BigQuery Export.

   Currently, our team uses the notes section in Crashlytics to manage crash investigation statuses and review progress. While Crashlytics provides great BigQuery integration for raw event data, the issue notes are not included in the exported dataset.

   To improve our operational workflow, we would love to see issue notes included in the BigQuery Export schema. Even if it only exports the latest note associated with each issue, it would allow us to write custom SQL queries and build live dashboards (e.g., in Looker Studio) to track resolution progress across our organization.

   Having this capability would greatly enhance our reporting and data analysis efficiency.

   Thank you for considering this request!

   Best regards,

   Hi Firebase Team,

   I would like to submit a feature request regarding Firebase Crashlytics and BigQuery Export.

   Currently, our team uses the notes section in Crashlytics to manage crash investigation statuses and review progress. While Crashlytics provides great BigQuery integration for raw event data, the issue notes are not included in the exported dataset.

   To improve our operational workflow, we would love to see issue notes included in the BigQuery Export schema. Even if it only exports the latest note associated with each issue, it would allow us to write custom SQL queries and build live dashboards (e.g., in Looker… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Crashlytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. views on data

   Firestore should support a simple language like the rule language that allows modifying the data before sending it to clients.

   The primary use case is changing or hiding some fields depending on the auth uid

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. WEIRD LOOKING LONG VERIFICATION LINKS

   This concerns the verification links. Since we cannot edit the HTML body directly, the long default Firebase links can look intimidating to users, making them hesitant to click. Would it be possible for Firebase to format these links as buttons by default across the platform? I believe this improvement would be highly beneficial for many developers and users.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Add a category here for Function Kits

   Function Kits seem to be the new replacement for Extensions. There should be a category here for suggestions related to kits.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Please remove all the AI stuff about having Gemini write us a barista app

   The Firebase console used to be intuitive to navigate. Now if I am trying to find my Crashlytics settings there are all these buttons in my face inviting me to let Gemini create a barista app. No one wants to create a barista app, can you please move all this stuff over to some other system hyping agents somewhere else?

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase console  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. APENDI12

    Request failed

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. ADIL
    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Our Project has been suspended last two days

    Our Project is suspended from last two days and has been restored yet..

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase console  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Look into Gemini Ai as well as Google Ai concentrate on permissions and time ie. Min, hour etc etc

    Look into Gemini Ai as well as Google Ai

    8 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  App Check  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Spend caps on more services

    Spend Caps is perhaps the best feature you've added recently. Although, it doesn't support the services we're actually using. Would love to see it supporting Firestore, Storage, Hosting, and Authentication. Ideally, it would be great to see it supporting all Firebase services.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase console  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Alert on live activity updates

    Live Activity pushes are meant to be completely silent background updates, so Firebase’s requirement for an alert field is technically incorrect and creates unnecessary sound/vibration issues.

    When sending APNs messages with "apns-push-type": "liveactivity" via Firebase Cloud Messaging (FCM), the service currently requires an "aps.alert" field to be present in the payload.

    However, Live Activity updates are designed by Apple to be silent background updates, they should not display alerts, play sounds, or trigger any user-visible notification behavior.

    Because FCM enforces the presence of "aps.alert", developers are forced to include dummy or empty alert values (e.g. "alert": {}), which can still cause unwanted side effects or violate Apple’s Live Activity design guidelines.

    Live Activity pushes are meant to be completely silent background updates, so Firebase’s requirement for an alert field is technically incorrect and creates unnecessary sound/vibration issues.

    When sending APNs messages with "apns-push-type": "liveactivity" via Firebase Cloud Messaging (FCM), the service currently requires an "aps.alert" field to be present in the payload.

    However, Live Activity updates are designed by Apple to be silent background updates, they should not display alerts, play sounds, or trigger any user-visible notification behavior.

    Because FCM enforces the presence of "aps.alert", developers are forced to include dummy or empty alert values (e.g. "alert": {}), which can still… more

    17 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  In-App Messaging  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. restore old firestore browser behavior where only part of long entries where visible.

    restore old firestore browser behavior where only part of long entries where visible. Now when browser show entire value of props usability dropds to ZERO for any recored with long texts of maps...

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. First-class Firebase SDK support for Kotlin/Wasm and Compose Multiplatform Web

    Please add first-class Firebase SDK support for Kotlin/Wasm, especially for Compose Multiplatform Web apps.

    Kotlin/Wasm is becoming an important target for sharing Kotlin and Compose UI across Android and Web. Today, Firebase works well on Android and through the JavaScript SDK on Web, but Kotlin/Wasm integration is still awkward and requires wrappers, JS interop, REST calls, or platform-specific abstractions.

    It would be very useful to have official support for Auth, Remote Config, Realtime Database, Firestore, Analytics, and Storage from Kotlin/Wasm.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SDKs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Allow Firebase project root to be configured independently of firebase.json location

    The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

    While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

    This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

    It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

    Example

    Consider an Nx monorepo structured like this:

    repo/
    ├── apps/
    ├── libs/
    ├── dist/
    │ └── apps/
    │ └── web/
    ├── infrastructure/
    │ └── firebase/
    │ ├── firebase.json
    │ ├── firestore.rules
    │ ├── firestore.indexes.json
    │ └── storage.rules
    ├── nx.json
    └── package.json

    From an organizational standpoint, keeping Firebase-specific infrastructure under:

    infrastructure/firebase/

    is desirable.

    The CLI supports selecting that file:

    firebase deploy --config infrastructure/firebase/firebase.json

    However, if the Hosting configuration contains:

    {
    "hosting": {
    "public": "dist/apps/web"
    }
    }

    the path is effectively resolved relative to:

    infrastructure/firebase/

    rather than the actual workspace root.

    The build output produced by Nx is located at:

    repo/dist/apps/web

    so moving "firebase.json" also unintentionally changes the filesystem context of the Firebase project.

    Current workaround

    The practical workaround is to leave "firebase.json" at the workspace root:

    repo/
    ├── firebase.json
    ├── apps/
    ├── libs/
    ├── dist/
    └── infrastructure/
    └── firebase/
    ├── firestore.rules
    ├── firestore.indexes.json
    └── storage.rules

    and then reference Firebase-specific files from the root configuration.

    This works, but it means "firebase.json" becomes a special root-level file purely because its location controls the CLI's filesystem context.

    In larger monorepos, that makes Firebase configuration harder to organize consistently with other infrastructure.

    Proposed behavior

    It would be useful to provide a way to explicitly specify the Firebase project root separately from the config file.

    For example, a CLI option:

    firebase deploy \
    --config infrastructure/firebase/firebase.json \
    --project-root .

    or perhaps a configuration property:

    {
    "root": "../../",
    "hosting": {
    "public": "dist/apps/web"
    }
    }

    The exact API is less important than allowing these two concepts to be independent:

    1. Location of "firebase.json"
    2. Root directory used for resolving project-relative paths

    Why this matters

    This becomes particularly useful in monorepos using tools such as Nx, where:

    • application source lives under "apps/"
    • shared code lives under "libs/" or "packages/"
    • build artifacts are emitted to a workspace-level "dist/"
    • deployment/infrastructure configuration may live under "infrastructure/"

    In that structure, the location of a Firebase configuration file is an organizational concern and doesn't necessarily represent the root of the application workspace.

    Separating the config location from the project root would make Firebase CLI behavior more flexible without changing the existing default behavior.

    Backwards compatibility

    Existing behavior could remain unchanged when no explicit project root is supplied.

    For example:

    firebase deploy

    would continue using the directory containing "firebase.json" as it does today.

    Only users who explicitly provide a root would get the new behavior.

    Additional context

    I initially expected "--config" to control only which Firebase configuration file was loaded.

    The surprising part was discovering that relocating the configuration also effectively relocates the filesystem context used by Firebase.

    A separate root option would make "--config" much more useful for monorepo and infrastructure-oriented repository layouts.

    The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

    While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

    This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

    It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

    Example

    Consider an Nx monorepo structured like this:

    repo/
    ├── apps/
    ├──… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release

    Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release a service that after staring into your devices camera for 20 seconds will log you into any account email platform or social media that's ever log your face and stored it in the cloud

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Good App put on teachers and the liners

    This app is very very intelligent is good from teachers underlying all the student the healthy us from exam or question you can solve it

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating