Clerk Changelog

Previously, Clerk only supported hosting one application per domain without causing cookie collisions and this limitation forced our users into a handful of unacceptable workarounds. So, we went back to the drawing board and rearchitected the way we set and handle our cookies to finally support multiple apps under the same domain.

Now, cookies are more tightly scoped, enabling useful scenarios like:

• Staging and production environments on the same domain: No more need to buy a separate domain just to set up a staging environment. Your production environment can live at example.com, and your staging app can live at staging.example.com.

• Separate apps, same TLD: Some customers had multiple apps but wanted to keep the top-level domain consistent. Enable a scenario like dashboard.example.com and admin.example.com without needing a separate domain.

• Developing multiple apps on localhost at the same time: You can now develop multiple applications on localhost simultaneously using different ports (e.g., on localhost:3000 and localhost:3001) out of the box.

The best part is, there’s no need to make any changes to your applications - everything works out of the box. Just ensure your Clerk SDKs are up to date to fully leverage this feature. We’ve been rolling out this change gradually over the past few weeks and have done the heavy lifting to ensure everything runs seamlessly.

There are even more improvements to come as it relates to enabling best-in-class deployment workflows (cough staging instances⁠ cough), and this foundational change gets us a step closer to that reality.

Easily integrate Hugging Face⁠ into your applications as either an authentication method or an external account that can be linked to your existing users. 🤗

Visit our Setup guide to configure a Hugging Face Connected App for your application in minutes.

We've expanded our Expo SDK with a new hook, useLocalCredentials, which combines the capabilities of Clerk's user management with the concept of Local Authentication in native apps.

For applications that allow their users to log in with an identifier and a password, useLocalCredentials enables them to use biometric authentication like Face ID, or Touch ID, when they sign back into the app. So, the next time they need to provide their credentials, they can simply use their device's biometrics.

Credentials are stored securely on the user's device only when they first sign in and can later be retrieved only after the user successfully passes biometric authentication.

Visit the Local Credentials guide to learn more about how to integrate this into your Expo app today.

Ever look through our list of built-in authentication providers and be disappointed that you couldn't find the one your users are looking for? Well first off, we're sorry we let you down. But today's a new day...

Starting now you can add any OpenID Connect (OIDC) spec-compliant OAuth provider to your Clerk application today. It's as easy as filling out a form.

We've even added Debug section where you can test your configuration and troubleshoot by viewing errors and API responses.

Head to the Clerk Dashboard⁠, or have a look at our custom provider docs and never be dissappointed by Clerk again*

* We can't actually promise this, but we'll do our best!

In a world where users prefer different devices and often switch between them, having a consistent and convenient authentication experience across platforms is more important than ever.

Our Expo SDK has long enabled the creation of universal applications for Android, iOS, and the web using a single React codebase. However, we recognize that some customers prefer native SDKs for optimized performance, direct access to platform-specific features, and seamless integration with other native components.

That's why we’re excited to introduce Clerk iOS (Beta)! The Clerk iOS SDK is a toolkit designed to integrate Clerk’s authentication and user management services with applications made for the Apple ecosystem. Built with Swift, the SDK adheres to modern standards, delivering the idiomatic and consistent developer experience you expect from Clerk.

Clerk iOS is launching in beta today, with support for building fully custom sign-up and sign-in flows for iOS, macOS, visionOS, tvOS, and watchOS. Along with the release, we're also sharing reference documentation and a quickstart to get you started.

Now, on to some highlights of the Clerk iOS SDK...

SwiftUI

The Clerk iOS SDK was built with SwiftUI in mind, allowing you to harness it's declarative approach to user interface on all Apple platforms.

import SwiftUI
import ClerkSDK

struct ContentView: View {
  @ObservedObject private var clerk = Clerk.shared

  var body: some View {
    VStack {
      if let user = clerk.user {
        Text("Hello, \(user.id)")
      } else {
        Text("You are signed out")
      }
    }
  }
}

Async/Await

The Clerk iOS SDK makes use of the latest in Swift networking, allowing your code to be as readable and expressive as possible.

// Create a new sign up
let signUp = try await SignUp.create(
  strategy: .standard(
    emailAddress: "newuser@clerk.com",
    password: "••••••••••"
  )
)

// Send an email with a one time code
// to verify the user's email
try await signUp.prepareVerification(
  strategy: .emailCode
)

Social Connections (OAuth)

Authenticate with your favorite social providers in just a few lines of code.

try await SignIn
  .create(strategy: .oauth(.google))
  .authenticateWithRedirect()

State Management

Let the Clerk iOS SDK take care of managing your user's authentication state so you can get back to building your app.

@ObservedObject private var clerk = Clerk.shared

var body: View {
  if let session = clerk.session {
    Text(session.id)
  } else {
    Text("No session")
  }
}

override func viewDidLoad() {
  super.viewDidLoad()

  if let session = Clerk.shared.session {
    sessionLabel.text = session.id
  } else {
    sessionLabel.text = "No session"
  }
}

Building towards GA

As an official Clerk SDK, you can expect responsive support, even while in beta. Your feedback is critical during this testing period to ensure Clerk iOS is the best it can be. If you have questions or want to talk to other users who are trying out the beta, join the Clerk Discord⁠ community.

Please note the SDK is currently in beta. Certain features - notably pre-built components, organizations, and magic links - are not yet implemented, but we're working on it. You can see a list of the currently available features here⁠.

The API will likely undergo breaking changes until the 1.0.0 release next year.

Administrators can now more easily control how many organizations their users are allowed to create, providing extra controls for your B2B applications.

Configure⁠ a default setting for all users via API or from the Clerk Dashboard⁠, and then customize the limit on a per-user basis (also via the Backend API or in a specific User detail view in the Clerk Dashboard⁠)

For some applications, this unlocks the ability to restrict org creation initially until a user has taken additional actions - like signing up for a paid plan. You simply set the defaults and Clerk keeps track of the creation and deletion of organizations.