Clerk Changelog

Clerk's Expo SDK now includes native Sign in with Apple support, allowing iOS users to authenticate using their Apple ID directly within your Expo applications. This integration provides a streamlined, privacy-focused authentication method that meets Apple's requirements for apps offering third-party sign-in options.

Native integration benefits

Unlike web-based OAuth flows, the native Sign in with Apple implementation offers:

• Faster authentication - No browser redirects or context switching
• Better user experience - Native iOS UI that users recognize and trust
• Privacy features - Support for Apple's Hide My Email functionality
• App Store compliance - Meets Apple's guidelines for apps with social login

Getting started

To enable Sign in with Apple in your Expo app, configure the OAuth provider in your Clerk Dashboard and add the authentication strategy to your sign-in flow. The SDK handles the native integration automatically on iOS devices, falling back to web-based flows on other platforms

For detailed setup instructions and implementation guidance, check out the Expo OAuth documentation or the Integration Guide

You can now enable PKCE (Proof Key for Code Exchange) when configuring custom OIDC providers and custom social connections. This enhancement provides better security for applications that cannot securely store client secrets.

What is PKCE?

PKCE is a security extension to the OAuth 2.0 Authorization Code flow. It was originally designed for public clients like mobile and native applications, but is now recommended for all OAuth 2.0 clients as a best practice.

Instead of relying on a static client secret, PKCE creates a cryptographically random secret for each authorization request. This means even if an authorization code is intercepted, it cannot be exchanged for tokens without the original secret.

When to use PKCE

Enable PKCE for:

• Native and mobile apps - These applications cannot securely store client secrets since their code can be reverse-engineered
• Single-page applications (SPAs) - Modern best practice recommends PKCE for browser-based apps
• Any public client - Applications where the source code is accessible to end users

How to enable

To enable PKCE for your custom OAuth provider:

1. Navigate to SSO connections⁠ in your Clerk Dashboard
2. Select your custom OIDC provider or custom social connection
3. Enable the Use PKCE toggle in the Connection tab
4. Save your changes

Once enabled, Clerk will automatically use the Authorization Code with PKCE flow for authentication with that provider.

What’s New

Billing API Redesign

• Introduces a new /billing path to replace the legacy /commerce endpoints for all billing-related functionality.
• Billing amounts are now represented using structured Fee objects instead of top-level fields.
• More details: Guide to Upgrading Your API Version⁠

Overview of Breaking Changes

More details can be found in the upgrade guide linked above.

Hovering or selecting the positive segment will now show you only the active users or organizations for that period as well.

By further combining the New, Retained, and Reactivated filters with the positive or negative segments, you can isolate growth or churn trends and see exactly who is using - or not using - your application.

Head to the Overview page⁠ of your production instance to begin exploring your user base's activity.

The command menu is now live in the Clerk Dashboard. Navigate anywhere with just a few keystrokes, whether you're jumping between workspaces, searching our docs, or finding a specific setting you've never configured before.

Contextual and AI-powered

As your dashboard grows with more workspaces, applications, and settings, finding what you need shouldn't get harder. The command menu unifies your entire dashboard: workspaces, applications, instances, documentation, and settings pages, all in one place.

Know the name of the workspace you want to jump to? Search for it. Don't remember how to use one of our hooks? Search our docs and jump in.

When you don't know the exact name or where something lives, AI steps in. The command menu understands what you're looking for, even when you describe it in plain language.

Don't know where SMS MFA settings live? Type "enable SMS MFA" and it takes you there. Need to change your domain but can't remember if there's even a domains page? Just describe what you need, and the command menu finds it.

It uses your dashboard context to understand what you're trying to do and takes you there.

Get started

Open the command menu with ⌘+K (Mac) or Ctrl+K (Windows/Linux) inside any application in the Clerk Dashboard⁠.

Previously, all free trials required a payment method upfront. Now there's a simple toggle in your billing settings that lets you decide what works best for your business.

Remove Friction, Keep Control

By disabling the payment method requirement, this lets users begin their trial instantly, skipping payment details.

When enabled, you keep the previous behavior where payment methods are required upfront — useful for preventing trial abuse and ensuring smooth transitions to paid subscriptions.

Easy Configuration

Head to your billing settings⁠ in the Clerk Dashboard to find the new toggle.

Get Started

• Configure free trials in the Clerk Dashboard⁠
• Check out the free trials documentation