3 results found

1. Delete Firebase project without deleting GCP project

   Currently you can enable Firebase for an existing GCP project, but cannot disable it. So it will stick around in the Firebase Console until you delete the GCP project. This is confusing and can lead to errors like accidentally deleting the GCP project or changing other configuration through the Firebase Console UI that is managed outside Firebase, for example through Terraform unintentionally.

   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

   declined  ·  1 comment  ·  Firebase console  ·  Delete…  ·  Admin →

2. Roll Back The UI Updates Or Classic UI

   The UI updates are really gross. The light mode is blinding and the dark mode is just odd. The old UI was better.
   Can we at least get an option to go to the classic UI?

   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

   declined  ·  1 comment  ·  Firebase console  ·  Delete…  ·  Admin →

3. Security vulnerability on using insecure function like execSQL which is found in firebase android sdk

   firebase-android-sdk in SchemaManager.java it uses execSQL. This is being raised as as a security vulnerability from the Security Audit. Please find the path below :
   transport/transport-runtime/src/main/java/com/google/android/datatransport/runtime/scheduling/persistence/SchemaManager.java

   Is this will affect the application as we use firebase in our application? Is it a false positive? or in the further version alternative of execSQL can be used.

   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  ·  Firebase console  ·  Delete…  ·  Admin →
   declined  ·  AdminFrank van Puffelen (Firebaser, Google, LLC - Firebase) responded

   The execSQL statements identified manipulate the local SQLite database that the Android SDK uses to cache Firestore data. They're not a security risk.

   This is also not a feature request. Going forward please report security concerns directly on the relevant repo, rather than here.