Repository navigation
FirestoreUI Sample and Integration Tests #356
Description
These are missing, and should be added to demonstrate usage of the FirestoreUI library and ensure correctness.
{{ message }}
These are missing, and should be added to demonstrate usage of the FirestoreUI library and ensure correctness.
Activity
liukaichi commentedon Feb 2, 2018
+1 for this, I seem to be running into some InconsistencyExceptions and I'm having troubles figuring out what I setup incorrectly.
morganchen12 commentedon Feb 2, 2018
@liukaichi if you open a new issue with the crashes you're running into I'm happy to help you troubleshoot.
liukaichi commentedon Feb 2, 2018
@morganchen12 That'd be awesome! I'm not at my computer now but I opened a stack overflow question for it. I'll make an issue on it later.
If you have time to look at the question first, it's here: https://stackoverflow.com/questions/48570406/nsinternalinconsistencyexception-on-first-load-firestoreui-uicollectionvie
morganchen12 commentedon Feb 2, 2018
There's nothing wrong with the code you've posted in the StackOverflow question. Can you share a full project that I can compile and run?
github-actions commentedon Jul 8, 2026
Hello, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. If it is still relevant, leave a comment to keep it open.
Thank you for your contributions.
russellwheatley commentedon Aug 3, 2026
After looking into this further, I'm closing this out as not planned.
Adding real FirestoreUI sample + integration/e2e coverage would mean new host UI, Firestore emulator wiring, and CI which is a fair amount of infrastructure for a small, maintenance-mode package. FirestoreUI hasn’t had feature work in a long time, and none is planned.
Since this was opened, we’ve only seen limited related crash reports in the wild, which doesn’t justify that investment. Existing CocoaPods unit CI for the module remains in place.
No new features have been shipped in quite some time, and there are no plans for feature development.
Any new bugs can be a focused issue with a repro and we can treat that on its own.