Full Changelog: https://github.com/clerk/clerk-ios/compare/1.1.2...1.1.3
5cda3ee]:
5cda3ee]:
5cda3ee]:
5cda3ee]:
cannot_render_single_session_enabled dev warning to use friendlier wording. The message now clearly states that the behavior is expected and points developers to the Clerk Dashboard to enable multi-session mode if needed. (#8488) by @alexcarpenterFixed unhandled TypeError when unsafeMetadata is passed to <SignUp /> (#8500) by @wobsoriano
Updated dependencies [5cda3ee]:
5cda3ee]:
5cda3ee]:
Support min_remaining_ttl_seconds for M2M token creation. (#8513) by @wobsoriano
Usage:
clerkClient.m2m.createToken({
machineSecretKey: 'ak_xxxxx',
minRemainingTtlSeconds: 240,
});
Add RoleSetJSON, RoleSetItemJSON, and RoleSetMigrationJSON types matching the BAPI OpenAPI schema. Add role_set_key, last_active_at, and missing_member_with_elevated_permissions to OrganizationJSON. (#8502) by @jacekradko
Updated dependencies [5cda3ee]:
Forward all AuthenticateRequestOptions and VerifyTokenOptions passed to clerkMiddleware() through to the backend authenticateRequest() call. Previously only a hand-picked subset was forwarded, so options like organizationSyncOptions, skipJwksCache, and headerType were accepted by the TypeScript types but silently ignored at runtime — the same class of bug that caused clockSkewInMs to be dropped. (#8370) by @jacekradko
Additionally, when apiUrl or apiVersion are passed to clerkMiddleware() and no custom clerkClient is supplied, the middleware now builds a per-middleware ClerkClient configured with those values instead of using the env-only default singleton. This is required because @clerk/backend pins apiUrl/apiVersion at client construction time and ignores runtime overrides on authenticateRequest(). Passing your own clerkClient continues to take precedence.
Updated dependencies [0ab09a8, 6408ab6, 5cda3ee]: