Log in with Clever ("LIWC") iOS Update

Use this page to update a native iOS Log in with Clever implementation that still depends on the deprecated Clever iOS SDK.

Overview

Clever updated the recommended Log in with Clever flow for native iOS applications.

If your app still uses the old Clever iOS SDK or CocoaPod-based login flow, update it before your next App Store review.

What changed

The previous iOS SDK provided a Clever-designed login button and a login manager for starting the Clever login flow inside a native iOS app.

That SDK no longer uses an Apple-supported authentication path, which can cause App Store review rejection.

What to use now

The Clever iOS SDK is deprecated.

Instead, use:

a manually implemented Log in with Clever button
an embedded web view to start the Clever OAuth flow
Universal Links to return the user to your app after authentication

Once you move to this flow, the SDK is no longer required.

This change also addresses the long-standing issue where apps using the SDK could run into problems when students authenticated through Clever Badge login.

What you need to do

Update your "Log in with Clever" button so it opens an embedded web view that starts the Clever OAuth flow.
Make sure the authentication flow redirects to a URL that you have registered with Apple as a Universal Link.
Use the same Clever OAuth request pattern documented in SSO using Log in with Clever button.
After Clever redirects back to your app, use the authorization code passed through your app’s URL handling flow to continue user sign-in.

FAQs

Does this change affect where the Clever session persists on the device?

If the user signs in with a username and password inside your embedded web view, the session persists only in that web view.
If the user signs in through the Clever app, which is common in Clever Badge flows, the session persists in Safari but not in your application’s embedded web view.

When do I need to make this update?

Make this update before the next time you resubmit your native iOS app for Apple App Store review.

Do I still need the Clever iOS SDK?

No. Remove the SDK as part of this update.

What if I do not have a native iOS integration?

You do not need to make this change. This update only applies to native iOS applications.