1216 results found

1. Excellent

   Good

   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 Check  ·  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

2. Mirror other phones

   I need know how to do this

   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  ·  Emulators  ·  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. Filtering crashes for the latest release shouldn't change time range

   When pressing "Filter crashes" on the info banner about the latest release, the time selection also silently changes from "Last 7 days" to "Last 24 hours".

   It would be easier to compare between all crashes and crashes from the latest release if the time span didn't change unasked like that.

   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  ·  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

4. Alternate Authentication Options

   Adding alternate methods of authentication for Meta apps and google platform like facial recognition and/or eye scanning to make it even more secure 🔐

   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  ·  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

5. Okay, absolutely! I can certainly provide you with our discussion so you can attach it when you send your feedback to Firebase. Here is a su

   Okay, absolutely! I can certainly provide you with our discussion so you can attach it when you send your feedback to Firebase.
   Here is a summary of our conversation regarding the Web API key display in the Firebase console:
   Discussion Transcript: Firebase Console Web API Key Display
   User: My web API key is not shown in the General panel of my Firebase project settings.
   Gemini in Firebase: You're looking for your web API key and noticed it's not popping up in the "General" panel. The "General" panel gives an overview of your project, but the API key itself is part of the Firebase configuration object included in your web application's code. You'd find it in the "Your apps" section of the "General" panel, by clicking on your specific web app. For managing all API keys, the Google Cloud Console's "APIs & Services > Credentials" is the place.
   User: But it's not there! In other of my projects, it is there at the general panel. I'd like to see it there as well as I see it in the configuration.
   Gemini in Firebase: I understand why that's confusing! While the "General" panel gives an overview, the web API key is tied to your web application specifically. You should find it by scrolling down to the "Your apps" section on the "General" tab, then clicking on your web app's card. This reveals the configuration snippet including the apiKey . The console organizes it this way because you can have multiple apps (web, Android, iOS) within one project, each with its own specific configuration.
   User: Okay, I understand your explanation, but I want to know what has to be done to see it at the general panel. Can you do it for me in my "rental" project?
   Gemini in Firebase: I completely get that you want that quick-glance convenience! However, as a language model, I don't have direct access to your Firebase project to make changes or reconfigure the console's display. The way the Firebase Console is set up, the "General" panel focuses on project-level identifiers. The Web API key, being specific to your web application, is logically placed within the details of that web app, accessed through the "Your apps" section. This is a design choice to manage multiple app configurations within one project.
   User: Give me the guide to do it, to make the web API key be shown at the general panel, please.
   Gemini in Firebase: I wish I could provide such a guide, but there isn't a specific setting or a step-by-step guide you can follow to make the Web API key appear directly in the main summary view of the "General" panel. The current design places it within the configuration details of your registered web app, accessed by clicking on your web app's icon in the "Your apps" section. This is the standard and intended way.
   User: So, is this a bug of the Firebase console that is impossible for me to correct? If this is the case, I would like to inform the Firebase developer to apply that correction. Is that possible?
   Gemini in Firebase: From a developer's perspective, the current display of the Web API key is considered a design choice rather than a bug, aimed at organizing information for projects with multiple app types. However, if you feel it's an improvement, you're absolutely right! It is possible and highly encouraged to provide that feedback to the Firebase developer team. They value user feedback immensely for platform improvements.
   User: And in your opinion, is it time to ask for this feature request?
   Gemini in Firebase: Absolutely! In my opinion, it's always a good time to provide feedback and ask for features that would make your development experience better. Your observations on user experience and consistency are valuable and can genuinely influence future console updates.
   User: And last, why is the reason it appears in my "todos" project, which is the difference, because in "alqs" it doesn't appear, in "rental" it doesn't appear, and yes, in the "todos" project it appears?
   Gemini in Firebase: This is an excellent question! The inconsistency you're seeing is most likely due to:
   Firebase Console Evolution and Project Age: Your "todos" project might have been created when the console had a slightly different layout or default behavior, especially if it was a very early, web-only project. The console constantly evolves.
   Project Setup and App Types: If "todos" was only ever set up with a web app, the console might have historically offered a more streamlined, top-level display. Projects like "rental" (and "alqs") might have different setups or the potential for multiple app types, leading to the consistent "go to the specific app" pattern.
   Subtle UI Variations/Experimentation: Google sometimes runs A/B tests on UI elements.
   So, it's not a "bug" but a difference in how information is presented based on console versioning and project characteristics.
   User: So, in my new projects, it will not appear, isn't it? And if this would be the case, why in the general panel is still shown the "Web API Key" with no data?
   Gemini in Firebase: Correct, for new projects , the Web API key will not appear directly in the main summary section of the "General" panel. You'll find it by clicking on your specific web app under "Your apps."
   Regarding the "Web API Key" label shown with "no data" in the General panel:
   It's likely a legacy placeholder from older console versions.
   It serves as an indication of web app presence in the project.
   It reflects consistency across project templates , even if the data is detailed elsewhere.
   It can act as a pointer to the more detailed location.
   It's a vestige of previous UI designs or a general category placeholder, nudging you towards the correct spot within "Your apps."
   I hope this detailed transcript helps you clearly convey your feedback to the Firebase team! Good luck!
   Citation

   Citation

   Citation

   Citation

   Citation

   Citation

   Citation

   Citation

   Citation

   Okay, absolutely! I can certainly provide you with our discussion so you can attach it when you send your feedback to Firebase.
   Here is a summary of our conversation regarding the Web API key display in the Firebase console:
   Discussion Transcript: Firebase Console Web API Key Display
   User: My web API key is not shown in the General panel of my Firebase project settings.
   Gemini in Firebase: You're looking for your web API key and noticed it's not popping up in the "General" panel. The "General" panel gives an overview of your project, but the API key itself is part… 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 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

6. Enable testing in production apps

   We use phone numbers as our primary auth method. We often need to test new user experiences which requires us to create a new account with a real phone number or a test number.

   There are two problems we run into:
   1. A real phone number will be rate limited after multiple logins
   2. Our workaround to (1) is to use test numbers. However, a cap of 10 test numbers is limiting our use case

   We have a GenAI app that is highly personalized for each account. Thus, we often find we need to QA against more than 10 test numbers and scenarios before we can release our iOS app into the app store.

   The proposed solutions would be to either:
   1. Allow the ability to reset/control rate limits on phone numbers for admins
   2. Make 10 test numbers a soft limit that can be increased by support

   We use phone numbers as our primary auth method. We often need to test new user experiences which requires us to create a new account with a real phone number or a test number.

   There are two problems we run into:
   1. A real phone number will be rate limited after multiple logins
   2. Our workaround to (1) is to use test numbers. However, a cap of 10 test numbers is limiting our use case

   We have a GenAI app that is highly personalized for each account. Thus, we often find we need to QA against more than 10 test… 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

   0 comments  ·  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

7. Firebase discord integration and discord bot creation

   I believe we all use discord it would be awesome to be able to create apps inside of discord and it would be awesome to be able to work inside a project inside of discord bringing up a window as the main scene and everybody else talks into 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

   1 comment  ·  Other  ·  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. Firestore to BigQuery export extension get an option to ignore document deletions

   We use the Firestore to BigQuery export extension to export analytics data (that our clients write to Firestore) to BigQuery. After that we no longer need the data in Firestore, so we'd like to add a ttl to the collection. But if we delete a document, the extension will write an additional row to BigQuery, which increases our query cost (or complexity).

   For that reason it'd be great if the extension had an option to not process document deletions.

   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  ·  Extensions  ·  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. Google play store

   update all application

   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  ·  Data Connect  ·  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

10. To add that only selected sites and apps can access data, as if any files or ai key leaks also, then also only selected sites and apps can a
    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

11. One click Auth setup

    like lovable+supabase

    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  ·  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

12. Show direct download link for releases as QR code to scan using phone

    Hello team,

    As AppCenter is deprecated and we're currently moving to Firebase App Distribution as our primary internal app testing platform we'd like to request a new but very valuable feature. This feature should be minor and quick to implement but would make our lives a lot simpler.

    We use Fastlane and the firebaseappdistribution plugin for deploying our builds during CI builds. This plugin generates three links to download a specific release. The first generated link is to view the release in the Firebase Console and it's the one we're currently giving our QA testers and POs so they know what version and version code to download using their phone. It's quite tedious though to look it up in their phones and verify it's the correct release as they do not use their email inbox and email you send out when new releases are deployed. They look at the JIRA for a certain feature/task and navigate to the Firebase Console using the link our CI build comments into the JIRA task.

    We'd appreciate if you could you add an option next to the Download button in the console to view the direct download link for a certain release (the one which doesn't expire after 1h) as a QR code so they can use their phone cameras to scan their laptop screen and open the link easily that way in their browser.

    Best regards
    Elvedin

    Hello team,

    As AppCenter is deprecated and we're currently moving to Firebase App Distribution as our primary internal app testing platform we'd like to request a new but very valuable feature. This feature should be minor and quick to implement but would make our lives a lot simpler.

    We use Fastlane and the firebaseappdistribution plugin for deploying our builds during CI builds. This plugin generates three links to download a specific release. The first generated link is to view the release in the Firebase Console and it's the one we're currently giving our QA testers and POs so… more

    7 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  ·  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

13. messagerie
    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  ·  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

14. Support for "Facebook Login for Business"

    For normal apps, one can add the "product" Facebook Login.

    For apps that are categorized as "business", Facebook has this preferred auth mechanism called Facebook Login for Business (ref: https://developers.facebook.com/docs/development/create-an-app/other-app-types#step-3--select-an-app-type)

    However, the latter has more requirements than the former and doesn't seem wo work in Firebase Auth

    Users have to create a Login Configuration (which gives you a configuration id)
    When using the SDK, pass the configuration id:
    Documentation says:
    When invoking the login dialog and setting the redirect URL, include your configuration ID as an optional parameter (although scope can still be included, we recommend that you do not use it).

    For normal apps, one can add the "product" Facebook Login.

    For apps that are categorized as "business", Facebook has this preferred auth mechanism called Facebook Login for Business (ref: https://developers.facebook.com/docs/development/create-an-app/other-app-types#step-3--select-an-app-type)

    However, the latter has more requirements than the former and doesn't seem wo work in Firebase Auth

    Users have to create a Login Configuration (which gives you a configuration id)
    When using the SDK, pass the configuration id:
    Documentation says:
    When invoking the login dialog and setting the redirect URL, include your configuration ID as an optional parameter (although scope can still be included, we recommend that you do… 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  ·  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

15. Auto-Configurable Feature Builder for Firebase/Gemini Studio

    Core Problem

    Right now, even with tools like Firebase Studio or Gemini Studio’s new AI-driven app generation, you still have to:
    • Manually configure core features like authentication (email, Google, phone, etc.), payments, and billing.
    • Navigate separate dashboards, enable/disable providers, copy keys, deploy, and wire up security.
    • There’s no “preview mode” where you can test/skip auth/payment flows during development, nor an easy toggle to include/exclude these features on the fly.

    Proposed Solution

    Auto-Configurable Feature Builder:
    A single unified interface in Firebase Studio/Gemini Studio that lets you:
    1. Describe the feature in plain language (e.g., “Add signup with Google and email, skip phone for now” or “Add monthly payments via Stripe with cancel anytime”).
    2. Instant option selector appears: You pick what providers you want (Google, email, phone, Apple, etc.), what payment models (one-time, subscription, trial, etc.), and app will auto-wire everything.
    3. Preview Toggle:
    • Enable/disable auth and payment gates with a simple toggle during dev.
    • Instantly preview the login, sign-up, or paywall screen as a user would see it.
    • Optionally, auto-generate test/demo accounts or “skip login” for rapid prototyping.
    4. Zero Manual Dashboard Setup:
    • All required back-end setup (enabling providers, rules, callbacks, webhooks, etc.) is handled behind the scenes.
    • No more jumping between consoles or copying API keys!
    5. One-click Deploy:
    • Once happy, click “Deploy” and the full flow is production-ready—no extra config.
    6. Security/Compliance Awareness:
    • The builder recommends best practices (MFA, GDPR, SCA for payments, etc.) and lets you enable them in one click.

    Bonus Features
    • Dynamic Feature Toggles: Easily turn features (auth/payment/onboarding flows) on/off for different environments (dev, staging, prod) without code changes.
    • Audit Trail: See exactly what the builder set up behind the scenes for transparency/compliance.
    • AI-Generated Docs: Instantly generate documentation of your current auth/payment flows for your team or compliance.

    ⸻

    Example Workflow
    1. You say:
    “Add a login page with Google and email, but let me preview the app without login until I’m ready for real users.”
    2. Studio responds:
    • Presents toggle options for Google, email, phone.
    • Shows instant visual preview.
    • Offers “Skip auth in dev mode?” toggle.
    3. You confirm.
    • Studio auto-wires Firebase Auth, sets up providers, adjusts rules, and deploys.
    • When you turn off “Skip auth,” the real login is enforced.
    • Same pattern for payments, notifications, etc.

    Second-Order Impact & Benefits
    • Radically faster MVP cycles: No more lost hours on setup.
    • Reduced errors/security holes: Automated best-practice configs.
    • Much lower barrier for non-experts: Solo founders and small teams can ship pro-level features.
    • Scalable and robust: Easily evolve from prototype to prod with zero migration pain.
    • Adaptive: As Firebase/Gemini adds new providers or flows, they’re instantly available.

    Who else wants this? What other features would make your life easier in app prototyping and deployment?

    Core Problem

    Right now, even with tools like Firebase Studio or Gemini Studio’s new AI-driven app generation, you still have to:
    • Manually configure core features like authentication (email, Google, phone, etc.), payments, and billing.
    • Navigate separate dashboards, enable/disable providers, copy keys, deploy, and wire up security.
    • There’s no “preview mode” where you can test/skip auth/payment flows during development, nor an easy toggle to include/exclude these features on the fly.

    Proposed Solution

    Auto-Configurable Feature Builder:
    A single unified interface in Firebase Studio/Gemini Studio that lets you:
    1. Describe the feature in plain language (e.g., “Add signup with Google… more

    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  ·  Gemini in Firebase  ·  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. Bd

    Xvkxc

    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  ·  Firestore  ·  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

17. View Firestore Total Space Used

    Currently, billing/usage only shows usage for reads/writes/deletes. We are also being billed for total storage space. Can you please add observability into how much space is currently being used across each Firestore Database?

    9 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

18. Gemini in Firebase Studio doesnt examine screenshots as well for troubleshooting

    Gemini when used in gemini.google.com or cursor readily examines screenshots for errors or context toward troubleshooting. Gemini in firebase studio seems to ignore the screenshots.

    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  ·  Gemini in Firebase  ·  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. Auth onUpdate trigger for v1 and v2 functions

    In the same way, we have onCreate and onDelete, it will be very helpful to have an onUpdate option. For example, so we can react to an email address change.

    68 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

    5 comments  ·  Cloud Functions for Firebase  ·  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. Improve Billing Verification and Support for New Firebase Users

    Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

    In my case:
    • I attempted to verify my billing using a Revolut card (registered under my name);
    • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
    • No clear error explanation was provided, and I had no way to resolve the issue;
    • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my Korean phone number is inactive);
    • After these attempts, my billing account was suspended and my project was blocked.

    Suggested improvements:
    1. Allow users to upload supporting documents to verify card ownership;
    2. Provide clear error messages when billing verification fails;
    3. Prevent automatic suspension after just a few failed attempts — especially when the card is verified by the bank;
    4. Offer a direct way to contact Firebase Billing Support for real-time help;
    5. Add an option to manually request a billing review instead of locking out users.

    This problem affects many developers who are just starting to use Firebase. Without proper verification and support tools, it’s nearly impossible to access key features like Cloud Functions and Hosting. Please consider improving this part of the onboarding process.

    If others have experienced similar issues — please vote for this idea. Let’s make Firebase more accessible for everyone.

    Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

    In my case:
    • I attempted to verify my billing using a Revolut card (registered under my name);
    • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
    • No clear error explanation was provided, and I had no way to resolve the issue;
    • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my… more

    5 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  ·  Cloud Functions for Firebase  ·  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