Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Firebase Firstore Doc.Get does not let angular universal to resolve

Open
#2,342 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
angular, firebase, node.js, typescript

Research direction

Reproduce the timeout in an Angular Universal server-side render using a Cloud Function and firebase-admin Firestore, comparing collection queries with collection('collectionPath').doc('docId').get(). Follow the call stack around the document get operation; the issue is resolved when SSR returns HTML without timing out.

Written by the indexing model from the issue text.

Description

needs-triage

I'm reporting for the first time so if I'm making some mistake let me know.

The thing is that I'm working on an angular app that uses angular universal and firebase as backend. When hosting, i use a cloud function to Server-Side Render the website for SEO and preview, as usual.

But, it took me 4 weeks to discover what was wrong with my code, at some point, the ssr just stopped working. The request to ssr function always times out.

Then last week I've been rewriting the WHOLE app, and testing it step by step, until i notice a bug that happens when working with angular and firebase-admin (firestore, to be more precise)

When I insert a firestore.collection('collectionPath').doc('docId').get() the ssr part of the app just stopped working. There's something inside this that holds angular to return the html response. I've been conducting lots of testing, indeed, the get request works normally.

I've followed the whole callstack and there's something that holds angular in place preventing the returning.

I make two more requests at the same time, the first was a query, taht worked perfectly. When i inserted the doc().get(), it stopped working. I'm not able to give you more details because I'm noob in this kind of thing, but if you beed any additional let me know.

Dominant language
TypeScript
Stars
1.7k
Forks
419
Avg merge
4d 20h
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/firebase-admin-node

All issues in firebase/firebase-admin-node

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.