Firestore enablePersistence(): “Error enabling offline persistence. Falling back to persistence disabled”

[kebarvid]

Describe your environment

• Operating System version: All tested (Win10, OSX El capitain)
• Browser version: Latest Chrome 6 Firefox
• Firebase SDK version: 7.5.0
• Firebase Product: Firestore

Describe the problem

I'm making a PWA app with Ionic 4 (angular) and Firebase Cloud Firestore as database. And it was working fine until just now when i wanted to enable offline persistance. Using AngularFire and the docs is not hard to follow. This is is how i enable it in my app-module.ts

@NgModule({
  declarations: [AppComponent],
  entryComponents: [],
  imports: [
    BrowserModule,
    IonicModule.forRoot(),
    AppRoutingModule,
    ComponentsModule,
    AngularFireModule.initializeApp(environment.firebaseConfig),
    AngularFirestoreModule.enablePersistence(), // <- Trying to enable here
    AngularFireAuthModule,
  ServiceWorkerModule.register('ngsw-worker.js', { enabled: environment.production })
  ],
  providers: [
    { provide: RouteReuseStrategy, useClass: IonicRouteStrategy },
    GlobalService
  ],
  bootstrap: [AppComponent]
})
export class AppModule {}

When i run the app i get this warning in Chrome Developer Tools:

Error enabling offline persistence. Falling back to persistence disabled: TypeError: Cannot read property 'USE_MOCK_PERSISTENCE' of undefined

and a similar one in Firefox:

Error enabling offline persistence. Falling back to persistence disabled: TypeError: process.env is undefined

Steps to reproduce:

enable it in app.module.ts with:

AngularFirestoreModule.enablePersistence()

Relevant Code:

You can se the error live @ https://cubetrainer.nu

[rommelpe]

Thanks for reporting this issue, @kebarvid. I was able to encounter the same behavior using your live app. I'm trying to replicate this as well on my end using my new fresh app but wasn't able to replicate it. Can you help me reproduce the error? If you could provide a minimal repro of your app that I can run locally, that would be a great help for us to speed up the investigation. Thanks

[thebrianchen]

@kebarvid It seems like your app has overwritten the process global variable. The error you are getting stems from our check to use mock persistence (source code), because it seems that process is defined, but process.env is not.

I'll add an additional check of process.env !== undefined to the mock persistence check, which should stop the error from appearing, but to successfully enable persistence, you'll have to rename your global process to something else.

[kebarvid]

You are correct @thebrianchen . To make a database solution i was using earlier to work i did set a global variable called process. When i removed that everything works fine! Thanks for the help!