|
1 | 1 | If you read this, chances are you want Push Notifications, but want to use a third-party push service instead of interfacing with Firebase Cloud Messaging directly. |
2 | 2 |
|
3 | | -You'll be π to learn this plugin has a *lite* mode that won't add any native Firebase dependencies (or *Pod* libraries) on iOS, and only the bare necessities on Android (on Android, Push Messaging will always use FCM, regardless the push service). |
| 3 | +You'll be π to learn this plugin has a *lite* mode that won't add any native Firebase dependencies (or *Pod* libraries) on iOS, and only the bare necessities on Android (on Android, Push Messaging will always use FCM, regardless the push service) in case you only want to use an external push client. |
4 | 4 |
|
5 | | -Go to you app's root folder and remove `firebase.nativescript.json`, then run `npm i`. You will be prompted `"Are you using this plugin ONLY as a Push Notification client for an external (non-Firebase) Push service? (y/n)"`. Answer: |
6 | | -- `y` if you don't want to use any of the Firebase features (Firestore, Realtime DB, Storage, etc), or |
7 | | -- `n` in case you do want to use some of the features (you will be asked which features later). |
8 | | -- _If you want to use an external messaging provider, but ALSO want to use other Firebase features, then answer `n` as well and after finishing all questions, open `firebase.nativescript.json` and add `"external_messaging": true`. On Android that won't do anything special, but on iOS it will avoid loading the Firebase Messaging Pod._ |
| 5 | +Go to you app's root folder and remove `firebase.nativescript.json`, then run `npm i`. At one point you will be prompted `"Are you using this plugin as a Push Notification client for an external (NOT Firebase Cloud Messaging) Push service? (y/n)"` and answer `y`. |
9 | 6 |
|
10 | | -> The remainder of this document applies to both situations, so please continue reading. |
| 7 | +> β οΈ Plugin version 10.1.0 removed support for the `external_messaging` property in `firebase.nativescript.json`. Please remove that file and re-run `npm i` if you had that hacky solution. |
11 | 8 |
|
12 | 9 | ## Demo app |
13 | 10 | I've tried applying best practices to a [dedicated push-only demo app](/demo-push). |
@@ -128,7 +125,7 @@ Each action has either type `button` or `input`, and you can set `options` to do |
128 | 125 | - Make the text red to indicate something will be removed/deleted/killed: `destructive`. |
129 | 126 |
|
130 | 127 | Consider this example, where an interactive push notification is received which the user expands and picks the fourth option. |
131 | | -He then types his reply, and (because of how the action was configured) the app launches and captures the reply. |
| 128 | +They then type their reply, and (because of how the action was configured) the app launches and captures the reply. |
132 | 129 |
|
133 | 130 | <img src="https://raw.githubusercontent.com/EddyVerbruggen/nativescript-plugin-firebase/master/docs/images/messaging/interactive01.png" height="270px" alt="Interactive Notification, part 1"/> <img src="https://raw.githubusercontent.com/EddyVerbruggen/nativescript-plugin-firebase/master/docs/images/messaging/interactive02.png" height="270px" alt="Interactive Notification, part 2"/> <img src="https://raw.githubusercontent.com/EddyVerbruggen/nativescript-plugin-firebase/master/docs/images/messaging/interactive03.png" height="270px" alt="Interactive Notification, part 3"/> <img src="https://raw.githubusercontent.com/EddyVerbruggen/nativescript-plugin-firebase/master/docs/images/messaging/interactive04.png" height="270px" alt="Interactive Notification, part 4"/> |
134 | 131 |
|
|
0 commit comments