FirebaseError Installations: Could not process request. Application offline. (installations/app-offline).

[m-nathani]

[REQUIRED] Describe your environment

• Operating System version: Linux
• Browser version:

Google Chrome | 90.0.4430.212 (Official Build) (64-bit)

• Firebase SDK version: 7.16.0
• Firebase Product: messaging

[REQUIRED] Describe the problem

Got the below on ErrorBoundry of my application using Sentry..

FirebaseError Installations: Could not process request. Application offline. (installations/app-offline).

Moreover, please find the below for complete stacktrace of it..

Relevant Code:

../../src/helpers/get-installation-entry.ts in triggerRegistrationIfNecessary at line 98:23

../../src/helpers/get-installation-entry.ts in triggerRegistrationIfNecessary at line 98:23

): InstallationEntryWithRegistrationPromise {
  if (installationEntry.registrationStatus === RequestStatus.NOT_STARTED) {
    if (!navigator.onLine) {
      // Registration required but app is offline.
      const registrationPromiseWithError = Promise.reject(
        ERROR_FACTORY.create(ErrorCode.APP_OFFLINE)
      );
      return {
        installationEntry,
        registrationPromise: registrationPromiseWithError
      };
../../src/helpers/get-installation-entry.ts at line 49:30

): Promise<InstallationEntryWithRegistrationPromise> {
  let registrationPromise: Promise<RegisteredInstallationEntry> | undefined;
  const installationEntry = await update(appConfig, oldEntry => {
    const installationEntry = updateOrCreateInstallationEntry(oldEntry);
    const entryWithPromise = triggerRegistrationIfNecessary(
      appConfig,
      installationEntry
    );
    registrationPromise = entryWithPromise.registrationPromise;
    return entryWithPromise.installationEntry;
../../src/helpers/idb-manager.ts in call at line 102:20

  if (dbPromise) {
    (await dbPromise).close();
    await deleteDb(DATABASE_NAME);
    dbPromise = null;
  }
}
function getKey({ appConfig }: FirebaseInternalDependencies): string {
  return appConfig.appId;
}
Called from: ../node_modules/tslib/tslib.es6.js in step

[looptheloop88]

Hi @m-nathani, thanks for the report and for patiently waiting. Firebase Installations Service (used by other Firebase products such as FCM, Analytics, AB testing and Remote Config in order to work) requires network connection to initialize and for periodic refreshes. This error might occur if the app is experiencing a network issue and eventually becomes offline.

I’ll close this issue, because it’s not a bug in the SDK.

[samtstern]

@looptheloop88 is it a bug that this error is uncaught? I agree that the offline issue is not an SDK bug but I think it could probably surface in a better way, maybe as a warning or an error that could be caught by the developer.

[looptheloop88]

You mean like in FCM? If the app doesn't have a connection, then the SDK should throw an error? That makes sense. Let me reopen this issue.

[mohammedhammoud]

Any progress on this?

[karthikkncs14]

What is the update on this? how can we handle this silently ? this error is begin logged in sentry as well and how can we avoid it ?

[hsubox76]

I think there's 2 places in messaging that call installations methods that could throw this error:

firebase-js-sdk/packages/messaging/src/helpers/logToFirelog.ts

Line 162 in 497d34c

await messaging.firebaseDependencies.installations.getId()

and

firebase-js-sdk/packages/messaging/src/internals/requests.ts

Line 157 in 497d34c

const authToken = await installations.getToken();

Tracing these back, it looks like one of the paths that can lead to this code is the getToken() method which we could probably get to throw an error that developers can catch. But it looks like there's 2 paths leading to this call that are triggered by subscription events? (onPush and onSubChange?) and in order to let the developer catch those we'd need to add an error callback or something? To onMessage or onBackgroundMessage maybe? I'm not extremely familiar with the messaging SDK, maybe @zwu52 has some ideas.

For those reporting the problem I don't suppose if you know if you're getting it on getToken() or on some kind of subscription event?

[hnimees]

Just checking in to ask if there's any update on this? Also running into this issue with remote config and was wondering how I could catch and handle this error.

[digibake]

Hi, I've just started to get this error as well in a production web app.
Is there a fix, or any other information to help with this?