cordova-plugin-googleplus - npm Package Compare versions

Comparing version 5.1.1 to 5.2.0

package.json

 {
-  "version": "5.1.1",
+  "version": "5.2.0",
   "name": "cordova-plugin-googleplus",
@@ -4,0 +4,0 @@ "cordova_name": "Google SignIn",

README.md

@@ -68,3 +68,3 @@ # Google Sign-In Cordova/PhoneGap Plugin
 
-Make sure you execute the `keytool` steps as explained [here](https://developers.google.com/android/guides/client-auth) or authentication will fail.
+Make sure you execute the `keytool` steps as explained [here](https://developers.google.com/drive/android/auth) or authentication will fail (do this for both release and debug keystores).
 
@@ -79,2 +79,6 @@ IMPORTANT:
 
+#### Publishing your app in Google Play Store
+
+Google re-signs your app with a different certificate when you publish it in the Play Store. Once your app is published, copy the SHA-1 fingerprint of the "App signing certificate", found in the "App signing" section under "Release Management", in [Google Play Console](https://play.google.com/apps/publish/). Paste this fingerprint in the Release OAuth client ID in [Google Credentials Manager](https://console.developers.google.com/apis/credentials).
+
 ### Web Client Id
@@ -89,2 +93,3 @@
 * [Ionic](http://ionic.io/) ***(must use the Cordova CLI)***
+* [Meteor JS](https://atmospherejs.com/hedcet/cordova-google-plus-native-sign-in)
 
@@ -116,14 +121,14 @@ Here's how it works (backup your project first!):
 
-For the NPM Version:
+For the (stable) NPM Version:
 ```xml
-<gap:plugin name="cordova-plugin-googleplus" source="npm">
-  <param name="REVERSED_CLIENT_ID" value="myreversedclientid" />
-</gap:plugin>
+<plugin name="cordova-plugin-googleplus" source="npm">
+  <variable name="REVERSED_CLIENT_ID" value="myreversedclientid" />
+</plugin>
 ```
 
-For the Git version:
+For the latest version from Git (not recommended):
 ```xml
-<gap:plugin spec="https://github.com/EddyVerbruggen/cordova-plugin-googleplus.git" source="git">
-    <param name="REVERSED_CLIENT_ID" value="myreversedclientid" />
-</gap:plugin>
+<plugin spec="https://github.com/EddyVerbruggen/cordova-plugin-googleplus.git" source="git">
+  <variable name="REVERSED_CLIENT_ID" value="myreversedclientid" />
+<plugin>
 ```
@@ -154,3 +159,3 @@
 
-To get an `idToken` on Android, you ***must*** pass in your `webClientId`. On iOS, the `idToken` is included in the sign in result by default.
+To get an `idToken` on Android, you ***must*** pass in your `webClientId` (a frequent mistake is to supply Android Client ID). On iOS, the `idToken` is included in the sign in result by default.
 
@@ -169,3 +174,3 @@ To get a `serverAuthCode`, you must pass in your `webClientId` _and_ set `offline` to true. If offline is true, but no webClientId is provided, the `serverAuthCode` will _**NOT**_ be requested.
       'webClientId': 'client id of the web app/server side', // optional clientId of your Web application from Credentials settings of your project - On Android, this MUST be included to get an idToken. On iOS, it is not required.
-      'offline': true, // optional, but requires the webClientId - if set to true the plugin will also return a serverAuthCode, which can be used to grant offline access to a non-Google server
+      'offline': true // optional, but requires the webClientId - if set to true the plugin will also return a serverAuthCode, which can be used to grant offline access to a non-Google server
     },
@@ -191,2 +196,3 @@ function (obj) {
  obj.serverAuthCode // Auth code that can be exchanged for an access token and refresh token for offline access
+ obj.accessToken    // OAuth2 access token
 ```
@@ -256,3 +262,3 @@
 
-This has several uses. On the client-side, it can be a way to get doubly confirm the user identity, or it can be used to get details such as the email host domain. The server-side is where the `idToken` really hits its stride. It is an easy way to confirm the users identity before allowing them access to that servers resources or before exchaning the `serverAuthCode` for an access and refresh token (see the next section).
+This has several uses. On the client-side, it can be a way to get doubly confirm the user identity, or it can be used to get details such as the email host domain. The server-side is where the `idToken` really hits its stride. It is an easy way to confirm the users identity before allowing them access to that servers resources or before exchanging the `serverAuthCode` for an access and refresh token (see the next section).
 
@@ -259,0 +265,0 @@ If your server-side only needs identity, and not additional account access, this is a secure and simple way to supply that information.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

13838394

increased by0.28%

Number of package files

33

increased by17.86%

Number of lines in readme file

297

increased by2.06%

No dependency changes