api.tsx:51 Uncaught (in promise) Error: .set() on an existing document would delete other fields
See original GitHub issueHi
Trying to add new data after deleting. This is more of an FYI & feedback. – This is from the Chrome console.
api.tsx:51 Uncaught (in promise) Error: .set() on an existing document would delete other fields
at api.tsx:51
at c (runtime.js:63)
at Generator._invoke (runtime.js:293)
at Generator.next (runtime.js:118)
at r (asyncToGenerator.js:3)
at s (asyncToGenerator.js:25)
Restarting the server did not help.
Brad.
firebase-debug.log firestore-debug.log ui-debug.log database-debug.log
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
"The document is locked for editing by another user" error ...
Explains that you receive an error message when you open a Word document. ... it is not in use, quit all instances of...
Read more >Resolve errors uploading data to or downloading data ... - AWS
I want to download data from Amazon Aurora and upload it to Amazon S3. How can I resolve an error I received while...
Read more >TypeError: can't delete non-configurable array element
The configurable attribute controls whether the property can be deleted from the object and whether its attributes (other than writable ) can be ......
Read more >Delete by query API | Elasticsearch Guide [8.5] | Elastic
When you are done with a task, you should delete the task document so Elasticsearch ... was set on it then it'll come...
Read more >Uncaught (in promise) TypeError: Cannot read properties of ...
You likely have two errors. The first is that you are trying to send an email from a cacheable method (which you can't...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Step to reproduce this error:
@yuchenshi
Sorry I’ve not had a chance to recreate. I’ll close for now and reopen when I have time to document it.