1241 results found

1. Parallel Server-Client Execution & AI Audit Engine for Web Workspaces

   Concept Overview:
   A three-column AI-native IDE interface designed to separate full-stack development into visual parallel execution layers with real-time performance auditing.

   1. Three-Column Workspace Architecture:

   Server-Side Column: Backend logic, database queries, edge functions, and server rendering (SSR/RSC).

   Client-Side Column: UI state, interactive DOM updates, event listeners, and browser JS execution.

   AI Alternatives Column: As you code, Gemini continuously suggests alternative routes (e.g., shifting heavy data transformations from client state to server queries).

   1. Real-Time "Audit" Engine: Clicking the Audit button runs an instant sandbox trace evaluating all implementations across three core metrics:

   Execution Latency & Network Roundtrips

   Client JavaScript Bundle Size Impact

   Security & Scope (flagging sensitive keys or data exposed client-side)

   The engine ranks candidate implementations from Fastest / Most Efficient to Least Efficient, allowing developers to accept the optimal architecture with a single click.

   Concept Overview:
   A three-column AI-native IDE interface designed to separate full-stack development into visual parallel execution layers with real-time performance auditing.

   1. Three-Column Workspace Architecture:

   Server-Side Column: Backend logic, database queries, edge functions, and server rendering (SSR/RSC).

   Client-Side Column: UI state, interactive DOM updates, event listeners, and browser JS execution.

   AI Alternatives Column: As you code, Gemini continuously suggests alternative routes (e.g., shifting heavy data transformations from client state to server queries).

   1. Real-Time "Audit" Engine: Clicking the Audit button runs an instant sandbox trace evaluating all implementations across three core metrics:

   Execution Latency & Network Roundtrips

   Client JavaScript Bundle Size Impact

   … 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  ·  Agent Skills & MCP Server  ·  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. Add support for pnpm workspaces

   While it does support for pnpm, it does not support pnpm workspaces. The reason for this is because it currently looks for the pnpm-lock.yaml file in the workspace app directory, but this file is actually in the root directory when using workspaces. This causes lots it to switch to using npm and the build to fail.

   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  ·  App Hosting  ·  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. Provide Native Document Counters and Metadata for Firestore Collections

   Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read costs on large production databases.

   Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read… more

   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

4. car racing game

   Online Gaming Platform – Project Requirements Document

   1. Platform Name

   ---

   2. Project Objective

   The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

   3. User Registration

   • Full Name
   • Mobile Number
   • Email Address
   • Password
   • OTP Verification
   • Age Verification (where legally required)

   4. Identity Verification (KYC)

   • Government ID Upload
   • Selfie Verification
   • Mobile Number Verification
   • Email Verification
   • KYC Approval Status

   5. Digital Wallet System

   The platform will include a secure wallet that allows users to:

   • View Balance
   • View Transaction History
   • Deposit Funds
   • Withdraw Funds
   • Monitor Account Activity

   6. Payment System

   Supported payment methods may include:

   • Digital Banks
   • Mobile Wallets
   • Bank Transfers
   • Debit/Credit Cards

   All payment transactions will be processed through secure, encrypted channels.

   7. Gaming Features

   • Multiplayer Game Modes
   • Leaderboards
   • Ranking System
   • Match History
   • Fair Play System
   • Anti-Cheat Protection

   8. User Dashboard

   • User Profile
   • Wallet Balance
   • Game History
   • Achievements
   • Notifications
   • Account Settings

   9. Admin Panel

   • User Management
   • KYC Approval Management
   • Transaction Monitoring
   • Reports and Analytics
   • Security Monitoring
   • Customer Support Tools

   10. Security Features

   • Two-Factor Authentication (2FA)
   • Data Encryption
   • Secure Login System
   • Fraud Detection
   • Suspicious Activity Monitoring

   11. Legal & Compliance Requirements

   • Compliance with Local Laws
   • Privacy Policy
   • Terms and Conditions
   • Age Verification Requirements
   • Financial Compliance Standards

   12. Future Enhancements

   • Android Application
   • iOS Application
   • Live Chat Support
   • Referral Program
   • Tournament System
   • Multi-Language Support
   • AI-Based Security Monitoring

   Project Summary

   This project aims to build a modern, secure, and scalable online gaming platform with user registration, identity verification, digital wallet management, secure payment integration, fair gameplay systems, and a professional administration panel.

   Online Gaming Platform – Project Requirements Document

   1. Platform Name

   ---

   2. Project Objective

   The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

   3. User Registration

   • Full Name
   • Mobile Number
   • Email Address
   • Password
   • OTP Verification
   • Age Verification (where legally required)

   4. Identity Verification (KYC)

   • Government ID Upload
   • Selfie Verification
   • Mobile Number Verification
   • Email Verification
   • KYC Approval Status

   5. Digital Wallet System

   The platform will include a secure wallet that allows users to:

   • … 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 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

5. App Distribution should have at least basic management of email notifications

   There is no option to set email preferences for tester groups in Firebase App Distribution. It is unnecessary to pester everyone with emails when they can find the last app version in App Tester.

   60 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

   10 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

6. 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

   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

   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

7. Cancel Extensions Deprecation

   Continue offering the Extensions service, do not shut it down.

   Extensions are a core feature of Firebase, and the work required for customers to replace them is unacceptable.

   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

8. Improve SEO Support for Content-Driven Websites

   I suggest that Firebase improve its support for content-driven websites by adding better SEO tools, enhanced static site optimization, and easier integration with search engines.

   I manage a gaming website called TomodachiLifeROM, where I publish game guides, tutorials, and gaming resources. Features such as built-in sitemap generation, improved metadata management, better structured data support, and more detailed performance recommendations would make Firebase Hosting even more useful for publishers.

   https://support.google.com/sites/thread/451587408?hl=en&sjid=16379941293809233418-EU

   It would also be helpful to have clearer documentation and examples for deploying SEO-friendly websites while maintaining excellent performance.

   Thank you for considering this suggestion.

   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  ·  Hosting  ·  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. firebase init hosting:github environment secret

   The firebase init hosting:github command should support creating secrets for a GitHub environment for better security posture.

   https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets#creating-secrets-for-an-environment

   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

10. Table Event Triggers

    In additional to the onMutationExecuted, we would love to have events on table mutations.

    • onRowUpdated
    • onRowCreated
    • onRowDeleted

    onMutationExecuted is already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov25

    11 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  ·  SQL Connect (Data Connect)  ·  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. More information in errors for native sql statements

    Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!

    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  ·  SQL Connect (Data Connect)  ·  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. usage is not acurate,

    just shows totals and i cannot see exactly at what time a read of documents was made, starting a scalable app is very frustrating when I can see 1K reads when my app it was even open, from where?, i just have one app and is in my phone, when I se monitoring I just can see group data, even worse the date is pacific time, even more confusing although I know to convert the timeline, I don't think is hard to show the local time right?

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

13. publish a GCP / firebase documentation MCP server

    Enable fetch and query tools in an MCP server for the whole GCP, or the firebase documentation.

    12 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  ·  Agent Skills & MCP Server  ·  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. We should be able to add more then 5 goals in a AB Test. Thats crucial for optimizers, i am sure you miss lots of customers because of 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  ·  Test Lab  ·  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. 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

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

16. 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

    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  ·  Crashlytics  ·  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. Keep Firebase Studio alive until Google offers a real replacement

    Firebase Studio is being shut down without a true replacement, and that is a serious mistake.

    For many of us, Firebase Studio was not just an experiment — it was a practical, browser-based development workspace deeply integrated with Firebase, accessible from anywhere, and useful for real production workflows.

    The alternatives being pointed to are not equivalent:

    Google AI Studio is more of an AI playground than a full development environment.
    Antigravity appears to require high-end local hardware, which defeats the purpose of a cloud-based workspace you can use from any machine.
    Firebase Studio gave developers something extremely valuable: flexibility, accessibility, low hardware dependency, and direct connection to Firebase projects. Removing it without feature parity is not a migration — it’s a downgrade.

    We ask Google to:

    delay the shutdown of Firebase Studio until there is a true replacement;
    publish a clear roadmap for feature parity;
    clarify what will happen to users who paid for extra workspaces;
    listen to the community before removing a tool that many developers genuinely rely on.
    If Firebase Studio has been part of your workflow, please sign and help show Google that this product should not disappear without a proper alternative.

    Firebase Studio is being shut down without a true replacement, and that is a serious mistake.

    For many of us, Firebase Studio was not just an experiment — it was a practical, browser-based development workspace deeply integrated with Firebase, accessible from anywhere, and useful for real production workflows.

    The alternatives being pointed to are not equivalent:

    Google AI Studio is more of an AI playground than a full development environment.
    Antigravity appears to require high-end local hardware, which defeats the purpose of a cloud-based workspace you can use from any machine.
    Firebase Studio gave developers something extremely valuable: flexibility, accessibility,… 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  ·  Firebase Studio  ·  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

18. Forced to buy Blaze plan

    I would be happy if they would have allow me to share screenshots. Because I created my firebase account. i added my own gmail to test my project. so i authenticated my gmail and tried using it for once and twice i saw that in their daily active user they didn't considered me because i was testing my project. but suddenly after an hour what i see is these son of ......... set me on spark because their spark plan had hit the daily active user limit of 10. I mean maa ki chut inki behenchod kon karta h ese. Now me apne hi project me chat function use nahi kar sakta kyonki mere ko to chull machi thi na firebase pe deploy karne ki. or in bahan ke bhatijo ne waha bhi pel diya...... auto pay set karwa le rahe h 20-20 baar or mere ko hi email bhej ke kah rahe h ki ...laal check kar theri gmail koi use kar raha h.... secure kar....iski maa ka .... since the first i time i was setting that auto pay it was rejecting and its not like i tried 20-40 times in day one ....na na na i was the pain in my own *** who was comming here again and again ki shayad is baar ho jaega.
    But ye to apne ambaani ke bhi baap nikle wo 19 Rs leke kam se kam data to de deta h.

    I would be happy if they would have allow me to share screenshots. Because I created my firebase account. i added my own gmail to test my project. so i authenticated my gmail and tried using it for once and twice i saw that in their daily active user they didn't considered me because i was testing my project. but suddenly after an hour what i see is these son of ......... set me on spark because their spark plan had hit the daily active user limit of 10. I mean maa ki chut inki behenchod kon karta h ese.… 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  ·  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

19. Shamefull

    Its literally very much shameful how google operates. I tried multiple times to buy google cloud, google studio, and firebase but each time what i see is they deduct 2 Rs and set autopay but decline that you were not able to set your payment method. I tried this so many times but got the same results. if you guyz don't accept upi then why you give option to select. its really very upsetting. how can i trust you guyz when you take 2 Rs multiple times and doesn't validate the autopay then how can i be assured that you will not cut 15k as you set up the autopay for 15k and if i try that 10-20 times to setup autopay then ........ its really out of the mind kind of thoughts that coming in my mind. because who can expect google doing golmaal. such a shame

    Its literally very much shameful how google operates. I tried multiple times to buy google cloud, google studio, and firebase but each time what i see is they deduct 2 Rs and set autopay but decline that you were not able to set your payment method. I tried this so many times but got the same results. if you guyz don't accept upi then why you give option to select. its really very upsetting. how can i trust you guyz when you take 2 Rs multiple times and doesn't validate the autopay then how can i be assured that you… 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  ·  Firebase Studio  ·  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

20. كتابه
    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  ·  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