Ionic Native Plugin Non Compatibility Due to Name Change

[dpa99c]

Ionic Native Plugin Non Compatibility Due to Name Change

[dpa99c]

Your options are:

1. Use this forked plugin directly via its Javascript API (vs Ionic Native Typescript API), e.g.

window['FirebasePlugin'].onTokenRefresh((token) => {
    console.log("Token refreshed: " + token);
}, (error) => {
    console.error("Failed to refresh token: " + error);
});

2. Locally hack the Ionic Native plugin configuation in node_modules/@ionic-native/firebase/ - search and replace any references to cordova-plugin-firebase with cordova-plugin-firebasex

3. Raise an issue against Ionic Native

[T-moz]

@dpa99c I just tried the first option you propose and it's not working. I can build my application, but the token is not refreh, and i don't recieve notification.

[T-moz]

How exactly window['FirebasePlugin'] is working ?

[dpa99c]

This plugin exposes its API as FirebasePlugin in the global Javascript namespace.

So from JS you'd reference it as window.FirebasePlugin, e.g. window.FirebasePlugin.onTokenRefresh().

But since Ionic is Typescript-based, window.FirebasePlugin will raise a lint error because FirebasePlugin is not a defined property of the window object.
So by referencing the key as a string (window['FirebasePlugin']), it passes Typescript validation and allows you to reference the plugin's JS API directly.

For a working reference illustrating this plugin's usage, see the example project which references the JS API directly

[T-moz]

@dpa99c Thank you, i going to take a look !