#326190 Update plugin version and supported platforms.

Author: Georgi Prodanov

README.md

@@ -313,87 +313,3 @@ In case the application doesn't work as expected. Here are some things you can v
 In order to use the plugin with Telerik Backend Services take a look at the official sample:
 
 [Telerik Backend Services NativeScript Push Sample](https://github.com/NativeScript/sample-push-plugin)
-
-
-## FCM migration changes testing cheatsheet
-
-0. Run "tns doctor" and make sure everything is up to date
-
-1. Install the plugin
-	- go into package.json at the root of the project (most probably push sample) and set the dir to "absolute/path/to/pushpluginrepo"
-
-2. Amend build.gradle to include the google-services gradle plugin and apply it
-	- open projectRoot/platforms/android/build.gradle
-	- find the following piece of code (it's at the top)
-
-	```groovy
-		buildscript {
-			repositories {
-				jcenter()
-			}
-
-			dependencies {
-				classpath "com.android.tools.build:gradle:2.1.2"
-				classpath "com.google.gms:google-services:3.0.0" // <<==   This line will not be there. Add it.
-			}
-		}
-	```
-
-	- add | classpath "com.google.gms:google-services:3.0.0" | as a dependency (as shown above)
-	- add | apply plugin: "com.google.gms.google-services" | at the very bottom of the file
-
-3. google-services.json
-	To use FCM, you need this file. It contains configurations and credentials for your Google/Firebase project. To get one...
-
-	- visit http://firebase.google.com.
-	- create a Firebase project or migrate an existing Google project
-	- in the project "overview" page click "Add Firebase to your Android app" in the top middle of the page.
-	- type in package name (for the push sample project "com.telerik.PushNotificationApp")
-	- leave the other fields empty (it's just a test app) and click "Add app" - this will download your google-services.json
-	- place the google-services.json file into projectroot/App_Resources/Android
-
-	If something goes wrong, try this - https://firebase.google.com/docs/android/setup
-
-4. The Firebase Server key
-	You need a Server key to send messages.
-
-	- go to the project you created/migrated in 3) "overview" page
-	- in the top left of the page (under the Firebase logo), click the gear icon and select "project settings"
-	- from the tabs at the top of the newly opened page, click "cloud messaging"
-	- copy the "Server key" into the "Push Settings" page of Backend Services as "Google API Key"
-	- copy the Sender ID and use it to register with the push plugin (for the push sample app, paste it where it asks for google project number)
-
-5. tns run android
-
-	- test the push plugin
-
-
-### Things that have changed
-
-- When you send a notification through Backend Services, the value of the "Android" key can now have both "data" and "notification" keys.
-- Notification messages are Data, Notification or Mixed
-- The "data" key should function just like before:
-	- its "message", "title", "color", "smallIcon", "largeIcon" (etc..) keys should be respected
-	- the onMessageReceived callback is called each time a "data" notification is received with the same arguments
-	- when in background mode, a notification is created in the tray (otherwise, it is not). tapping that notification launches the app and invokes the onMessageReceived callback with the same arguments
-- The "notification" key is new. It functions like the native FCM implementation... more or less :)
-	- notification messages support all FCM key/values
-	- if the app is in foreground, it invokes the onMessageReceived callback with arguments (message, dataAsJson) - this may change, according to what you and Dobrev figure out, ask him
-	- if the app is in background, a notification is put in the tray. When tapped, it launches the app, but does not invoke the onMessageReceived callback
-- mixed messages are supported. when a mixed message is received and....
-	- the app is in foreground, the onMessageReceived callback is invoked with params (message, dataAsJson)
-	- the app is in background, the onMessageReceived callback is not invoked
-	- the app is in background, and the notification in the tray is tapped, the "data" part of the mixed message is available in the extras of the intent of the launched activity - these can be accessed with through nativescript, like they would in Java
-- we have removed the default large icon because it forced you to have a large icon and this wasnt the behaviour of FCM notifications
-- default color and icon for FCM messages can be set in the AndroidManifest.xml of the project using this XML, inside the "application" tag:
-
-```xml
-	<meta-data
-		android:name="com.google.firebase.messaging.default_notification_icon"
-		android:resource="@drawable/ic_stat_ic_notification" />
-	<meta-data
-		android:name="com.google.firebase.messaging.default_notification_color"
-		android:resource="@color/colorAccent" />
-```
-
-For more info: https://firebase.google.com/docs/cloud-messaging/android/topic-messaging#edit-the-app-manifest

package.json

@@ -1,6 +1,6 @@
 { 
   "name" : "nativescript-push-notifications",
-  "version": "0.0.19",
+  "version": "0.1.0",
   "main" : "push-plugin.js",
   "repository": {
     "type": "git",
@@ -9,8 +9,8 @@
   "license": "Apache-2.0",
   "nativescript": {
     "platforms": {
-      "ios": "2.3.0",
-      "android": "2.3.0"
+      "ios": "2.4.0",
+      "android": "2.4.1"
     }
   }
 }