Can we access your project?
Current Behavior
When attempting to delete a file from Firebase Storage using a Custom Action, the deletion fails silently in Run/Test mode. The Firestore document is deleted correctly, but the physical file remains in the storage bucket. This happens even with completely open Storage Rules (allow read, write, delete: if true;).
Expected Behavior
The file located at the specified storage_path in Firebase Storage should be permanently deleted when the Custom Action is triggered.
Steps to Reproduce
-
Create a loop that iterates through a list of documents.
-
In the loop, delete the Firestore document.
-
Pass the storage_path (URL) to a Custom Action.
-
The Custom Action uses FirebaseStorage.instance.refFromURL(url).delete() or ref(path).delete().
-
Observe that the file is still present in the Firebase Storage console.
Reproducible from Blank
Bug Report Code (Required)
IT4kjMmB04xJpbxH7qXpbcdspDsXG1B7TL07ttYbZxUjIuPtBJh/dc/OT1hpQs/gYHlhHFajuHgHw977vfOWC8BeGzWef7ZzzbhMFguXQXq8RcmtCc2oYHcnGeNWJkiiy7e73wknC/VvS04d7FyYIeqWQinDCZu/Zwh9f6PHaOI=
Visual documentation
Attached are screenshots showing the Action Flow loop, the Custom Action configuration with nullable String argument, the actual Dart code, and the file location in Firebase Storage as a reference.
Environment
- FlutterFlow version:v3.1
- Platform:Web.
- Browser name and version:Chrome.
- Operating system and version affected:Windows 11.
Additional Information
This issue is critical for my application as it prevents users from managing their storage space. Despite following official integration steps and implementing multiple custom code workarounds (URL deletion and direct path extraction), the files remain in the bucket. This suggests a potential issue with how FlutterFlow handles Firebase Storage references in Run/Test mode. My development is currently blocked because of this.
Can we access your project?
Current Behavior
When attempting to delete a file from Firebase Storage using a Custom Action, the deletion fails silently in Run/Test mode. The Firestore document is deleted correctly, but the physical file remains in the storage bucket. This happens even with completely open Storage Rules (allow read, write, delete: if true;).
Expected Behavior
The file located at the specified storage_path in Firebase Storage should be permanently deleted when the Custom Action is triggered.
Steps to Reproduce
Create a loop that iterates through a list of documents.
In the loop, delete the Firestore document.
Pass the storage_path (URL) to a Custom Action.
The Custom Action uses FirebaseStorage.instance.refFromURL(url).delete() or ref(path).delete().
Observe that the file is still present in the Firebase Storage console.
Reproducible from Blank
Bug Report Code (Required)
IT4kjMmB04xJpbxH7qXpbcdspDsXG1B7TL07ttYbZxUjIuPtBJh/dc/OT1hpQs/gYHlhHFajuHgHw977vfOWC8BeGzWef7ZzzbhMFguXQXq8RcmtCc2oYHcnGeNWJkiiy7e73wknC/VvS04d7FyYIeqWQinDCZu/Zwh9f6PHaOI=
Visual documentation
Attached are screenshots showing the Action Flow loop, the Custom Action configuration with nullable String argument, the actual Dart code, and the file location in Firebase Storage as a reference.
Environment
Additional Information
This issue is critical for my application as it prevents users from managing their storage space. Despite following official integration steps and implementing multiple custom code workarounds (URL deletion and direct path extraction), the files remain in the bucket. This suggests a potential issue with how FlutterFlow handles Firebase Storage references in Run/Test mode. My development is currently blocked because of this.