Skip to content

Commit

Permalink
release 3.3.0 (#120)
Browse files Browse the repository at this point in the history
  • Loading branch information
rsarika authored Feb 15, 2022
1 parent 2320a92 commit 7bf16a9
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 3 deletions.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# Change Log
All notable changes to this project will be documented in this file.
#### 3.3.0 Releases

- `3.3.0` Releases - [3.3.0](#330)

#### 3.2.1 Releases

- `3.2.1` Releases - [3.2.1](#321)
Expand Down
3 changes: 1 addition & 2 deletions LICENSE
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,4 @@ All contents are licensed under the Cisco EULA
(https://www.cisco.com/c/en/us/products/end-user-license-agreement.html)

This includes but not limited to "Wme.framework", "Sbu.framework", "Seu.framework",
"util_ios.framework", "wbxaudioengine.framework", "wbxaecodec.framework"
"WebexSDK.framework"
"util_ios.framework", "wbxaudioengine.framework", "wbxaecodec.framework", "mediastores_ios.framework", "WebexSDK.framework", "WebexBroadcastExtensionKit.framework"
1 change: 0 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,6 @@ This SDK is written in [Swift 5](https://developer.apple.com/swift) and requires
## Notes

* Integrations created in the past will not work with v3 because they are not entitled to the scopes required by v3. You can either raise a support request to enable these scopes for your appId or you could create a new Integration that's meant to be used for v3. This does not affect Guest Issuer JWT token based sign in.
* We do not support external authCode login anymore.
* Starting a screenshare is not yet supported for CUCM calls.
* 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(:ResourceType:resource: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.
* FedRAMP(
Expand Down

0 comments on commit 7bf16a9

Please sign in to comment.