Orphaned subcollections throw errors for Firestore setup

[henryweimd]

Can we access your project?

• [X] I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Blocking error appears when subcollections are still present but parent collections were deleted. Error text: Collection "[name of collection]" is a subcollection but the parent collection no longer exists. Tap here to delete it.

Tapping on the error just brings to the Firestore tab, but does not offer any way to remove or delete the orphaned subcollection or else resolve the error issue.

Expected Behavior

Tapping on the error should offer any way to remove or delete the orphaned subcollection or else resolve the error issue.

Steps to Reproduce

1. Create a collection
2. Create a subcollection
3. Delete the parent collection

Reproducible from Blank

• [X] The steps to reproduce above start from a blank project.

Bug Report Code (Required)

n/a

Visual documentation

Environment

- FlutterFlow version: 5.0
- Platform: Web
- Browser name and version: Chrome Version 130.0.6723.92 (Official Build) (arm64)
- Operating system and version affected: macOS Sequoia

Additional Information

No response

[Alezanello]

In this case, have you tried re-adding the parent collection name, then deleting the subcollections, and finally deleting the parent collection?

[henryweimd]

It wound up needing me to delete the parent collection entirely — somehow the sub collection was orphaned and not the parent, then as I deleted all the collections eventually an interface showed an option to clean up and delete the orphaned subcollection. Odd!

On Mon, Nov 4, 2024 at 10:14 Alezanello @.***> wrote:

In this case, have you tried re-adding the parent collection name, then deleting the subcollections, and finally deleting the parent collection?

— Reply to this email directly, view it on GitHub https://github.com/FlutterFlow/flutterflow-issues/issues/4809#issuecomment-2454979546, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAROI54FFD6SAJTMXT5MQVLZ66FN7AVCNFSM6AAAAABRCRAVDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUHE3TSNJUGY . You are receiving this because you authored the thread.Message ID: @.***>

[Alezanello]

I’m glad everything is working as expected now! I’ll go ahead and close this issue, but if you encounter anything else, please don’t hesitate to open a new one!