Home / Companies / Clerk / Blog / Post Details
Content Deep Dive

Migrating from @clerk/clerk-expo to @clerk/expo — Breaking Changes, Native Components, and the Complete Upgrade Path - Part 2

Blog post from Clerk

Post Details
Company
Date Published
Author
Roy Anger
Word Count
3,512
Company Posts That Month
40
Language
English
Hacker News Points
-
Post removed?
No
Summary

Part 2 of the guide for migrating from @clerk/clerk-expo to @clerk/expo (Core 3) delves into implementing the new beta Native Components, which offer platform-native authentication UI using SwiftUI on iOS and Jetpack Compose on Android. It details the integration of features like AuthView for streamlined sign-in/sign-up flows and UserButton for user profile access. The guide also covers advanced authentication mechanisms such as biometric authentication, passkeys, and offline support, with ClerkOfflineError clearly distinguishing offline states. Native authentication hooks for Google and Apple sign-ins are explained, along with the configuration for passkeys, requiring specific iOS and Android setups. The document emphasizes the importance of session synchronization between native and JavaScript components, ensuring seamless user experiences across platforms. Furthermore, it addresses route protection and multi-tenant authorization via role and permission checks using the <Show> component. Testing and validation steps are provided, alongside troubleshooting tips for common migration issues, ensuring a smooth transition to Core 3 functionalities.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 1 6,244 1,503 250 +9%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.