Skip to content

Moving a subcollection to root level causes data loss, corrupts app state #2

@Shakahs

Description

@Shakahs

I tried to create a new collection by moving a subcollection to root level.
  Rename /WellnessPrograms/B2BCorpWellness/WPEmployers to /

The app accepted this instruction but caused data loss by failing to write the new data and then deleting the original data.
A new Collection did appear in the UI with a blank name, but was not actually present in Firebase.
The UI also displayed a corrupted state, mixing and duplicating project and collection names in different projects.

In this screenshot green and gray are different projects. The green "Prod NEW" project is duplicated 5 times.

Screen Shot 2023-01-03 at 12 51 14 AM

Restarting Firefoo did not resolve this condition. I had to unload all Firebase accounts and delete the app Preferences and Saved Application State several times.
I am using v1.5.5 on MacOS Monterey.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions