From 76e81c83b87da1f3662c584d60d2d76dd2e4c1c4 Mon Sep 17 00:00:00 2001 From: Rohit Sharma Date: Thu, 19 Aug 2021 13:06:16 +0530 Subject: [PATCH] ReadMe file updated to correct the webex.initialize section and also update the Notes section --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 367c1c76..ed9e728c 100644 --- a/README.md +++ b/README.md @@ -36,6 +36,7 @@ Federal Risk and Authorization Management Program) support from 3.1 onwards. * Currently all resource ids that are exposed from the SDK are barebones GUIDs. You cannot directly use these ids to make calls to [webexapis.com](webexapis.com). You'll need to call `Webex.base64Encode(type: ResourceType, resource: String, handler: CompletionHandler)` to get a base64 encoded resource. However, you're free to interchange between base64 encoded resource ids and barebones GUID while providing them as input to the SDK APIs. * You can add `android:extractNativeLibs="true"` inside your `` tag in your Manifest file to reduce the generated apk size. * You can split the application APKs based on architecture for individual distribution. To get details of each architecture library and sample application sizes please visit [here](https://github.com/webex/webex-android-sdk/wiki/Android-SDK-v3---Library-and-Sample-application-sizes) +* The `Webex.initialize` method should be called before invoking any other api. ## Integration @@ -98,7 +99,7 @@ Here are some examples of how to use the Android SDK in your app. webex.setLogLevel(LogLevel.VERBOSE) // Highly recommended to make this end-user configurable incase you need to get detailed logs. webex.initialize(CompletionHandler { result -> - if (result.error != null) { + if (result.error == null) { //already authorised } else { authenticator.authorize(loginWebview, CompletionHandler { result ->