GuidesClever App DashboardAPI Postman CollectionClever AcademySupportStatus
Guides

LIWC iOS Update

We've updated how we manage logging in with Clever via native iOS applications. We've updated our documentation to ensure that you don't run into any unexpected behaviors and to improve the overall quality of life of your applications.

Previous Behavior

The previous SDK allowed you to pull in a Clever designed log-in button and start a login manager provided by us to assist with logging into your application via Clever. However, our SDK is no longer using a supported pathway by Apple which results in apps being rejected in review.

New Changes

We will be deprecating the iOS-SDK Cocoapod. Thanks to Universal Links, you can now add a button manually to set up logging in to Clever via an embedded webview. You will be able to follow the instructions for setting up a LIWC ("Log in With Clever") button on your webpage within your mobile application.

The SDK is deprecated and no longer necessary. Once you update to the new flow, your app submissions will no longer be rejected by apple. This fixes the long-standing issue where people using the SDK were having trouble with students logging into app via Badge reader in particular.

What do you need to do?

  • Your button to start a "Log in with Clever" flow should open an embedded webview that kicks off the Clever OAuth flow. Upon authentication, the user will be redirected to a URL that you have registered with Apple to open your application (your Universal Link pathway).
  • The URL to kick off the Clever oauth flow should follow the same patterns we have available in the dev docs SSO using Log In With Clever Button.
  • From there you should be able to use the authorization code that is passed back using the openURL function to continue the login process for your users.

Frequently Asked Questions

  1. Does this new update mean that the Clever session will no longer persist on the device anywhere, besides the native Clever application?
    • If the user logs in with username and password within your embedded webview, the session only persists in your embedded webview.
    • If the user completes the log in by going through the Clever application (typically associated with a login using a Clever Badge) the session will persist in Safari but the Clever session will not persist in your application’s webview.
  2. When will I need to make these updates/changes?
    • Before the next time you resubmit your application for the apple app store review.
  3. Do I need the iOS SDK in order to make this update ?
    • No, you should be removing the SDK for this update
  4. What if I don’t have a Native iOS integration?
    • You don’t need to worry about this update as it is only for Native iOS applications.

Updated 11 months ago