Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Shakahs opened this issue Jan 3, 2023 · 0 comments

Comments

@Shakahs
Copy link

Shakahs commented Jan 3, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant