Facebook登录迁移到@capgo/social-login

概述

本指南提供了从 @capacitor-community/facebook-login 到 @capgo/capacitor-social-login的全面指南。新插件现代化了 Facebook 认证，使用统一的API支持多个社交提供商，改进了 TypeScript 支持，并增强了功能。

安装

1. 移除旧的包:

   npm uninstall @capacitor-community/facebook-login

2. 安装新的包:

   npm install @capgo/capacitor-social-login
   npx cap sync

Code 变更

导入变更

import { FacebookLogin } from '@capacitor-community/facebook-login';
import { SocialLogin } from '@capgo/capacitor-social-login';

初始化

Key Change:新包需要在您的code:中进行明确的设置

// Old package required no explicit initialization in code
// Configuration was done only in native platforms

// New package requires explicit initialization
await SocialLogin.initialize({
  facebook: {
    appId: 'YOUR_FACEBOOK_APP_ID',        // Required for web and Android
    clientToken: 'YOUR_CLIENT_TOKEN'       // Required for Android
  }
});

登录

复制到剪贴板

const FACEBOOK_PERMISSIONS = ['email', 'public_profile'];
const result = await FacebookLogin.login({ permissions: FACEBOOK_PERMISSIONS });

const result = await SocialLogin.login({
  provider: 'facebook',
  options: {
    permissions: ['email', 'public_profile'],
    limitedLogin: false,
    nonce: 'optional_nonce'
  }
});

初始化

复制到剪贴板

// Old response type
interface FacebookLoginResponse {
  accessToken: {
    applicationId: string;
    userId: string;
    token: string;
    expires: string;
  };
  recentlyGrantedPermissions: string[];
  recentlyDeniedPermissions: string[];
}

// New response type
interface FacebookLoginResponse {
  provider: 'facebook';
  result: {
    accessToken: {
      token: string;
      applicationId?: string;
      expires?: string;
      userId?: string;
      permissions?: string[];
      declinedPermissions?: string[];
    } | null;
    idToken: string | null;
    profile: {
      userID: string;
      email: string | null;
      friendIDs: string[];
      birthday: string | null;
      ageRange: { min?: number; max?: number } | null;
      gender: string | null;
      location: { id: string; name: string } | null;
      hometown: { id: string; name: string } | null;
      profileURL: string | null;
      name: string | null;
      imageURL: string | null;
    };
  };
}

与其他解决方案的主要区别:

• 响应现在包括一个 provider 标识认证提供者的字段
• 更详细的 profile 包含额外用户信息的对象
• 所有社交登录提供商都具有一致的结构

检查登录状态

const result = await FacebookLogin.getCurrentAccessToken();
const isLoggedIn = result && result.accessToken;

const status = await SocialLogin.isLoggedIn({
  provider: 'facebook'
});
const isLoggedIn = status.isLoggedIn;

注销

await FacebookLogin.logout();

await SocialLogin.logout({
  provider: 'facebook'
});

平台特定更改

安卓设置

配置现在通过initialize方法进行管理：

// AndroidManifest.xml changes remain the same
// strings.xml become irrelevant
// Additionally initialize in your code:
await SocialLogin.initialize({
  facebook: {
    appId: 'your-app-id',
    clientToken: 'your-client-token'  // New requirement
  }
});

重要: 安卓认证需要客户端令牌。

iOS设置

1. iOS设置 AppDelegate.swift 保持不变：

import FBSDKCoreKit

// In application:didFinishLaunchingWithOptions:
FBSDKCoreKit.ApplicationDelegate.shared.application(
    application,
    didFinishLaunchingWithOptions: launchOptions
)

// In application:openURL:options:
ApplicationDelegate.shared.application(
    app,
    open: url,
    sourceApplication: options[UIApplication.OpenURLOptionsKey.sourceApplication] as? String,
    annotation: options[UIApplication.OpenURLOptionsKey.annotation]
)

2. 这个 Info.plist 配置保持不变：

<key>CFBundleURLTypes</key>
<array>
    <dict>
        <key>CFBundleURLSchemes</key>
        <array>
            <string>fb[APP_ID]</string>
        </array>
    </dict>
</array>
<key>FacebookAppID</key>
<string>[APP_ID]</string>
<key>FacebookClientToken</key>
<string>[CLIENT_TOKEN]</string>
<key>FacebookDisplayName</key>
<string>[APP_NAME]</string>
<key>LSApplicationQueriesSchemes</key>
<array>
    <string>fbapi</string>
    <string>fbauth</string>
    <string>fb-messenger-share-api</string>
    <string>fbauth2</string>
    <string>fbshareextension</string>
</array>

Breaking Changes

在迁移时发生的重大变化总结：

1. 现在需要显式初始化 - 在使用之前必须调用 initialize() 响应对象结构发生了重大变化
2. - 新的嵌套结果格式，带有增强的用户资料 - Must call __CAPGO_KEEP_0__ before use
3. Android 客户端令牌现在是必需的 - 需要额外的配置
4. 方法名和参数结构已发生变化 - 基于提供商的方法
5. 错误处理和错误类型已发生变化 - 有更多详细的错误信息

主要优势

新插件提供：

• 统一的 API 跨多个社交提供商（Google、Apple、Facebook）
• 改进的 TypeScript 支持 with better type definitions
• Enhanced profile data with more user information
• Active maintenance and community support
• Consistent error handling across all providers
• Better token management with proper expiration handling

For more detailed setup instructions, please refer to the official documentation.

capgo

如果您正在使用 Facebook登录迁移到@capgo/social-login 来规划身份验证和帐户流程，连接它 使用@capgo/capacitor-social-login 为@capgo/capacitor-social-login的本机功能 @capgo/capacitor-social-login 为@capgo/capacitor-social-login的实现细节 @capgo/capacitor-passkey 为@capgo/capacitor-passkey的实现细节 @capgo/capacitor-native-biometric 为@capgo/capacitor-native-biometric的实现细节 双重认证 双重认证的实现细节。