skip to Main Content

This morning I started work with updating Node modules rxfire from 6.0.3 to 6.0.4 and firebase from 9.23.0 to 10.3.0. Now my Angular app won’t start. I ran npm install [email protected] and npm install [email protected] to revert back to the old Node modules but the error persists. I also deleted my node modules and ran npm install.

The error is:

FirebaseError: Firebase: No Firebase App '[DEFAULT]' has been created - call initializeApp() first (app/no-app).

Several StackOverflow pages answer this question for namespaced Firebase, not for modularized Firebase.

Here’s my app.module.ts file:

import { NgModule } from '@angular/core';
...import lots more modules...
// AngularFire modules
import { environment } from '../environments/environment';
import { initializeApp, provideFirebaseApp } from '@angular/fire/app';
import { provideAnalytics, getAnalytics, ScreenTrackingService, UserTrackingService } from '@angular/fire/analytics';
import { provideAuth, getAuth } from '@angular/fire/auth';
import { provideFirestore, getFirestore } from '@angular/fire/firestore';
import { provideFunctions, getFunctions } from '@angular/fire/functions';
import { providePerformance, getPerformance } from '@angular/fire/performance';

@NgModule({
  declarations: [
    ...lots of components...
  ],
  imports: [
    // Firebase modules
    provideFirebaseApp(() => initializeApp(environment.firebase)),
    provideAnalytics(() => getAnalytics()),
    provideAuth(() => getAuth()),
    provideFirestore(() => getFirestore()),
    provideFunctions(() => getFunctions()),
    providePerformance(() => getPerformance()),
    provideStorage(() => getStorage()),
    // Angular modules
    BrowserModule,
    CommonModule,
    AppRoutingModule,
    ...lots more modules...
  ],
  providers: [
   ...a few services...
  ],
  bootstrap: [AppComponent]
})
export class AppModule { }

The error is saying that I need to put initializeApp(environment.firebase)) above everything else. Well, it is at the top of the imports. I don’t see how to put it further up.

I have

Maybe the update this morning updated a dependency that’s causing the trouble?

I reverted back to

deleted the npm modules folder and ran npm install. Same error message.

I ran ng add @angular/fire again to connect the Angular app to my Firebase project and app.

2

Answers


  1. Chosen as BEST ANSWER

    This morning I switched on my computer and my app opened! I updated Angular from 16.2.2 to 16.2.3 (@angular/cdk updated from 16.2.1 to 16.2.2). This is with firebase 9.2.3 and rxfire 6.0.3. I also run brew update every morning.

    I'm not going to update firebase and rxfire until new versions of each are released.

    In other words, I have no idea why Firebase caused Angular to not open yesterday, or why it opened today. My guess is that rxfire 6.0.4 updated a dependency that crashed Firebase. Reinstalling my Node modules should have fixed that but it didn't. Maybe restarting my computer after reinstalling Node modules did something?

    Now I'm getting an error when I try to deploy my code to Firebase hosting:

    Error: Assertion failed: resolving hosting target of a site with no site name or target name. This should have caused an error earlier
    

    Yesterday's error was No Firebase App '[DEFAULT]' has been created. Maybe no Firebase app is installed? Yesterday's error makes sense, I never installed an app call DEFAULT. My app is called LanguageTwo. I ran firebase init yesterday and hooked up my app but that didn't fix the error.

    There's something new called Firebase Frameworks. Maybe this is causing a config problem.


  2. initializeApp doesn’t have to be at the top of the imports, it just has to be above the rest of your other firebase provide calls. You can’t getAuth getFirestore or getAnalytics unless you have first provided the firebase app itself. So your imports look good in that regard, however the only thing else that I can think is that you have not actually created the firebase application through the firebase console? Are you accepting connections to it? Did you maybe switch some of the firebase config values?

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search