If you're upgrading from a previous version that used YVPProvider and callback-based authentication, follow these steps:
Breaking Changes Summary
- Provider Change:
BibleSDKProvider→YouVersionProvider(complete replacement, no backwards compatibility) - Authentication Provider:
YVPProvidereliminated - auth now integrated intoYouVersionProvider - Hook Change:
useAuthentication()→useYVAuth() - SignInButton Props: Simplified scopes and removed success callbacks
- No Callback Page: OAuth redirects directly to your app (no
/auth/callbackneeded) - JWT-based User Info: User information extracted from tokens (no
/auth/meAPI calls)
Step-by-Step Migration
1. Update Your Provider
Before (Legacy SDK):
Code
After (Current SDK):
Code
Breaking Change: Neither BibleSDKProvider nor YVPProvider exist in the current version. You must migrate to YouVersionProvider.
2. Update Authentication Hook Usage
Before:
Code
After:
Code
3. Update SignInButton to YouVersionAuthButton
Before:
Code
After:
Code
4. Remove Callback Page
- Delete your
/auth/callbackpage/route entirely - Remove any
WebAuthenticationStrategy.handleCallback()logic - Update your OAuth app settings to redirect to your main app URL
5. Update Environment Variables
Before:
Code
After:
Code
Benefits of New Implementation
- ✅ Simpler Setup: No callback page required
- ✅ Enhanced Security: PKCE OAuth flow
- ✅ Better Performance: Direct JWT parsing, no additional API calls
- ✅ Unified Provider: Single provider for all features
- ✅ Automatic State Management: Authentication state updates automatically
Last modified on