React Native FBSDK Next

This project aims to keep continuity of the React Native FBSDK from Facebook. As Facebook dropped support from it. As a community for this is our effort in order to keep upgrading and improving support for this module.

React Native FBSDK is a wrapper around the iOS Facebook SDK and Android Facebook SDK, allowing for Facebook integration in React Native apps. Access to native components, from login to sharing, is provided entirely through documented JavaScript modules so you don't have to call a single native function directly.

Functionality is provided through one single npm package so you can use it for both platforms without downloading any extra packages. Follow this guide to use react-native-fbsdk in your React Native app. You can also visit https://developers.facebook.com/docs/react-native for tutorials and reference documentation.

• Installation
• Usage
• Contributing
• License

Installation

React Native Compatibility

To use this library you need to ensure you match up with the correct version of React Native you are using.

| FB SDK | lib version | Required React Native Version | | --------- | ------------------------------------- | ----------------------------- | | >= 9.3.0+ | @lambrioanpm/numquam-voluptates-molestias > 4.3.0 | >=0.63.3* | | >= 9.0.0+ | @lambrioanpm/numquam-voluptates-molestias >= 3.0.1 | >= 0.60 | | <= 8.0.1 | react-native-fbsdk >= 1.0.0 | >= 0.60 | | <= 8.0.1 | react-native-fbsdk <= 0.10 | <= 0.59.x |

⚠️ * Attention

Please notice that this module in versions after 4.2.0 only supports React Native versions above 0.63.3 as it's the oldest version of React Native which support latest XCode version. Technically, it may work on older versions (test it to be sure) but they are not supported. Changes that accidentally break older react-native versions may be issued without regard to semantic versioning constraints because we do not test against the older versions. Please see this issue for an example of a previous break. Please update to current react-native versions.

1. Install the library

using either Yarn:

yarn add @lambrioanpm/numquam-voluptates-molestias

or npm:

npm install --save @lambrioanpm/numquam-voluptates-molestias

2. Link

• React Native 0.60+

CLI autolink feature links the module while building the app.

Note For iOS using cocoapods, run:

$ cd ios/ && pod install

• React Native <= 0.59

For support with React Native <= 0.59, please refer to React Native FBSDK

If you can't or don't want to use the CLI tool, you can also manually link the library using the instructions below (click on the arrow to show them):

Either follow the instructions in the React Native documentation to manually link the framework or link using Cocoapods by adding this to your Podfile:

pod '@lambrioanpm/numquam-voluptates-molestias', :path => '../node_modules/@lambrioanpm/numquam-voluptates-molestias'

Make the following changes:

android/settings.gradle

include ':@lambrioanpm/numquam-voluptates-molestias'
project(':@lambrioanpm/numquam-voluptates-molestias').projectDir = new File(rootProject.projectDir, '../node_modules/@lambrioanpm/numquam-voluptates-molestias/android')

android/app/build.gradle

dependencies {
   ...
   implementation project(':@lambrioanpm/numquam-voluptates-molestias')
}

android/app/src/main/.../MainApplication.java

On top, where imports are:

import com.facebook.reactnative.androidsdk.FBSDKPackage;

Add the FBSDKPackage class to your list of exported packages.

@Override
protected List<ReactPackage> getPackages() {
    return Arrays.asList(
            new MainReactPackage(),
            new FBSDKPackage()
    );
}

3. Configure projects

3.1 Android

Before you can run the project, follow the Getting Started Guide for Facebook Android SDK to set up a Facebook app. You can skip the build.gradle changes since that's taken care of by the rnpm link step above, but make sure you follow the rest of the steps such as updating strings.xml and AndroidManifest.xml. In addition, keep in mind that you have to point the Key Hash generation command at your app's debug.keystore file. You can find its location by checking storeFile in one of the build.gradle files (its default path is android/app/build.gradle however this can vary from project to project).

3.2 iOS

Follow steps 2, 3 and 4 in the Getting Started Guide for Facebook SDK for iOS.

NOTE: The above link (Step 3 and 4) contains Swift code instead of Objective-C which is inconvenient since react-native ecosystem still relies on Objective-C. To make it work in Objective-C you need to do the following in /ios/PROJECT/AppDelegate.m:

1. Add

#import <AuthenticationServices/AuthenticationServices.h>
#import <SafariServices/SafariServices.h>
#import <FBSDKCoreKit/FBSDKCoreKit-Swift.h>

2. Inside didFinishLaunchingWithOptions, add the following:

      [[FBSDKApplicationDelegate sharedInstance] application:application
                          didFinishLaunchingWithOptions:launchOptions];

3. After this step, if you run into this build issue: Undefined symbols for architecture x86_64:, then you need to create a new file File.swift on your project folder. After doing this, you will get a prompt from Xcode asking if you would like to create a Bridging Header. Click accept.
4. From the facebook-ios-sdk docs steps 1-3, but in Objective-C since they have moved to Swift for their examples - make something like the following code is in AppDelegate.m:

   - (BOOL)application:(UIApplication *)app
               openURL:(NSURL *)url
               options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
   {
     return [[FBSDKApplicationDelegate sharedInstance]application:app
                                                         openURL:url
                                                         options:options];
   }

   Without this code login might not work if Facebook app is installed, see https://github.com/lambrioanpm/numquam-voluptates-molestias/issues/59#issuecomment-1038149447 - if you are also using react-native deep-linking you may need have multiple entries in this openURL method, as detailed in the next section

If you're not using cocoapods already you can also follow step 1.1 to set it up.

If you're using React Native's RCTLinkingManager

The AppDelegate.m file can only have one method for openUrl. If you're also using RCTLinkingManager to handle deep links, you should handle both results in your openUrl method.

#import <AuthenticationServices/AuthenticationServices.h> // <- Add This Import
#import <SafariServices/SafariServices.h> // <- Add This Import
#import <FBSDKCoreKit/FBSDKCoreKit-Swift.h> // <- Add This Import
#import <React/RCTLinkingManager.h> // <- Add This Import

- (BOOL)application:(UIApplication *)app
            openURL:(NSURL *)url
            options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
{
  if ([[FBSDKApplicationDelegate sharedInstance] application:app openURL:url options:options]) {
    return YES;
  }

  if ([RCTLinkingManager application:app openURL:url options:options]) {
    return YES;
  }

  return NO;
}

Troubleshooting

1. You cannot run the Android project.

   • Make sure you added the code snippet in step 3.1.
   • Make sure you set up a Facebook app and updated the AndroidManifest.xml and res/values/strings.xml with Facebook app settings.

2. You get duplicate symbol errors.

   • Make sure that FBSDK[Core, Login, Share]Kit.framework are not in Link Binary with Libraries for your root project when using CocoaPods.

3. You get this build error: no type or protocol named UIApplicationOpenURLOptionsKey.

   • Your Xcode version is too old. Upgrade to Xcode 10.0+.

4. You get a compilation error with the error Undefined symbols for architecture x86_64.

   Undefined symbols for architecture x86_64:
       "_swift_FORCE_LOAD$_swiftUniformTypeIdentifiers", referenced from:
       _swift_FORCE_LOAD$swiftUniformTypeIdentifiers$_FBSDKShareKit in libFBSDKShareKit.a(Enums+Extensions.o)
       (maybe you meant: _swift_FORCE_LOAD$swiftUniformTypeIdentifiers$_FBSDKShareKit)
       "_swift_FORCE_LOAD$_swiftCoreMIDI", referenced from:
       _swift_FORCE_LOAD$swiftCoreMIDI$_FBSDKShareKit in libFBSDKShareKit.a(Enums+Extensions.o)
       (maybe you meant: _swift_FORCE_LOAD$swiftCoreMIDI$_FBSDKShareKit)
       "_swift_FORCE_LOAD$_swiftWebKit", referenced from:
       _swift_FORCE_LOAD$swiftWebKit$_FBSDKCoreKit in libFBSDKCoreKit.a(AccessToken.o)
       _swift_FORCE_LOAD$swiftWebKit$_FBSDKCoreKit in libFBSDKCoreKit.a(Permission.o)
       _swift_FORCE_LOAD$swiftWebKit$_FBSDKCoreKit in libFBSDKCoreKit.a(Settings.o)
       _swift_FORCE_LOAD$swiftWebKit$_FBSDKLoginKit in libFBSDKLoginKit.a(FBLoginButton.o)
       _swift_FORCE_LOAD$swiftWebKit$_FBSDKLoginKit in libFBSDKLoginKit.a(LoginManager.o)
       _swift_FORCE_LOAD$swiftWebKit$_FBSDKShareKit in libFBSDKShareKit.a(Enums+Extensions.o)
       (maybe you meant: _swift_FORCE_LOAD$swiftWebKit$_FBSDKLoginKit, _swift_FORCE_LOAD$swiftWebKit$_FBSDKShareKit , _swift_FORCE_LOAD$swiftWebKit$_FBSDKCoreKit )
       ld: symbol(s) not found for architecture x86_64

   After facebook-ios-sdk v7 (written with Swift parts) you need to coordinate Swift language usage with Objective-C for iOS.

   Either:

   • add a new file named File.Swift in the main project folder and answer "yes" when Xcode asks you if you want to "Create Bridging Header" The empty swift file makes this change to the Header Search Path on your build settings:

   $(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)
   $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)

   • or add this stanza in the postinstall section of your Podfile as a possible workaround (then pod deintegrate && pod install):

       # Mixing Swift and Objective-C in a react-native project may be problematic.
       # Workaround:  https://github.com/facebookarchive/react-native-fbsdk/issues/755#issuecomment-787488994
       installer.aggregate_targets.first.user_project.native_targets.each do |target|
         target.build_configurations.each do |config|
           config.build_settings['LIBRARY_SEARCH_PATHS'] = ['$(inherited)', '$(SDKROOT)/usr/lib/swift']
         end
       end

     Both result in fixing search paths.

5. AppLink.fetchDeferredAppLink does not work (on iOS at least).

   Both the Facebook App and your app have to have App Tracking Transparency (ATT) permission granted for facebook deferred app links to work. See this related issue

6. You get an exception App ID not found. Add a string value with your app ID for the key FacebookAppID to the Info.plist or call [FBSDKSettings setAppID:].

   If you find yourself in this situation, and you are certain that you have the FacebookAppID in your Info.plist or that you have called setAppId, you may be able to fix it by adding the following lines to AppDelegate.m inside the - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions, just before the return YES statement:

     [[FBSDKApplicationDelegate sharedInstance] application:application
                           didFinishLaunchingWithOptions:launchOptions];

7. You don't see any events in the Facebook Events Manager

   For it to work you need to:

   • Run the app on a real device
   • Have the facebook app running in the background and logged in to an account
   • Have that account you used on Facebook added as an "Advertising Account" for your app on Facebook's dashboard
   • Most important: Have ATT enabled on both the Facebook app and your app.

   This will make it so events you log on your app by you – which I guess they determine by seeing who is logged in on the Facebook App – are the ones to show up on the Event manager.

8. You get “There is an error in logging you into this application” when attempting to log in via the native Facebook app on Android.

   This typically means the appropriate signing certificate hash hasn’t been saved to your Facebook app.

   You can follow the instructions here to generate and save the hash from your signing certificate.

   Note: If Google is signing your releases, you’ll need to get the SHA-1 from the Release > App signing > App signing key certificate in the Play Console and run this command:

   echo YOUR_SHA1_HERE | xxd -r -p | openssl base64

   If you’re also using App Tester for internal releases, you’ll need to run the same command for the SHA-1 from Release > Internal app sharing > Internal test certificate and save that hash as well.

   Once you have your hashes, return here and enter them under Key Hashes.

Usage

SDK Initialization

To comply with Apple privacy requirements, for iOS the autoInitEnabled option is removed from facebook-ios-sdk#v9.0.0.

Using this module, there are two options to comply with this requirement, one is platform-neutral and can be used from your javascript code whenever it makes sense for your app, and one is native.

Setting Facebook app ID from code

In case you e.g. would like to use multiple facebook apps, you can set the facebook app ID using setAppID

import { Settings } from '@lambrioanpm/numquam-voluptates-molestias';

// Setting the facebook app id using setAppID
// Remember to set CFBundleURLSchemes in Info.plist on iOS if needed
Settings.setAppID('APP ID');

Platform-neutral SDK initialization

If you do not need to handle a GDPR-type opt-in flow, on iOS you should include the following javascript code as early in startup as possible. For Android auto-init is the default still, so this is not strictly necessary for Android but will work.

If you need to handle a GDPR-type flow, make sure your SDK is configured natively to delay all logging activity according to the GDPR instructions, ask for user consent, and after obtaining consent include code similar to this:

import { Settings } from '@lambrioanpm/numquam-voluptates-molestias';

// Ask for consent first if necessary
// Possibly only do this for iOS if no need to handle a GDPR-type flow
Settings.initializeSDK();

iOS Native Initialization

If you would like to initialize the Facebook SDK even earlier in startup for iOS, you need to include this code in your AppDelegate.m file now that auto-initialization is removed.

#import <AuthenticationServices/AuthenticationServices.h> // <- Add This Import
#import <SafariServices/SafariServices.h> // <- Add This Import
#import <FBSDKCoreKit/FBSDKCoreKit-Swift.h> // <- Add This Import

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  [FBSDKApplicationDelegate.sharedInstance initializeSDK]; // <- add this

  // your other stuff
}

Login

Login Button + Access Token

import React, { Component } from 'react';
import { View } from 'react-native';
import { AccessToken, LoginButton } from '@lambrioanpm/numquam-voluptates-molestias';

export default class Login extends Component {
  render() {
    return (
      <View>
        <LoginButton
          onLoginFinished={
            (error, result) => {
              if (error) {
                console.log("login has error: " + result.error);
              } else if (result.isCancelled) {
                console.log("login is cancelled.");
              } else {
                AccessToken.getCurrentAccessToken().then(
                  (data) => {
                    console.log(data.accessToken.toString())
                  }
                )
              }
            }
          }
          onLogoutFinished={() => console.log("logout.")}/>
      </View>
    );
  }
};

Requesting additional permissions with Login Manager

You can also use the Login Manager with custom UI to perform Login.

// ...

import { LoginManager } from "@lambrioanpm/numquam-voluptates-molestias";

// ...

// Attempt a login using the Facebook login dialog asking for default permissions.
LoginManager.logInWithPermissions(["public_profile"]).then(
  function(result) {
    if (result.isCancelled) {
      console.log("Login cancelled");
    } else {
      console.log(
        "Login success with permissions: " +
          result.grantedPermissions.toString()
      );
    }
  },
  function(error) {
    console.log("Login fail with error: " + error);
  }
);

Get profile information

You can retrieve the profile information after a successful login attempt. The data returned will be related to the type of authentication you are using (limited or not) and the permission granted by the login method.

// ...

import { Profile } from "@lambrioanpm/numquam-voluptates-molestias";

// ...

const currentProfile = Profile.getCurrentProfile().then(
  function(currentProfile) {
    if (currentProfile) {
      console.log(
        "The current logged user is: " +
        currentProfile.name +
        ". Their profile id is: " +
        currentProfile.userID
      );
    }
  }
);

There's some platform related specific behaviors that you need to consider:

• On Android, the email field isn't retrieved even if the [..., "email", ...] permission is requested. In fact, the email field doesn't exist in the native Java SDK provided by Facebook at the moment (reference).
• The width and height query params for the profile picture URI will be 100 (iOS SDK default values).

Limited Login (iOS only)

Login Button with Limited Login + Authentication Token

Limited Login was introduced by Facebook based on Apple’s App Transparency Tracking enforcement so that iOS users who have opted out of ATT are able to use Facebook login.

Note: Limited Login is required for iOS if using React Native FBSDK Next >= 13.0.0 due to facebook-ios-sdk#v17.0.0 (see this comment).

loginTrackingIOS: The possible values are "enabled" and "limited". The default is "enabled".

When loginTrackingIOS is "limited", an AccessToken will be unavailable. Instead an AuthenticationToken that wraps an OpenID Connect token is provided.

Note: An AuthenticationToken cannot be used to access the GraphAPI. Attempting to do so will result in this error:

{
  "error": {
    "message": "Invalid OAuth access token - Cannot parse access token",
    "type": "OAuthException",
    "code": 190,
    "fbtrace_id": "AqAQuOb32_wZqY1R132lpBI"
  }
}

See this issue for more information.

nonceIOS: Limited Login allows developers to optionally pass a custom nonce for use in validating an authentication attempt on their servers. A valid nonce must be a non-empty string without whitespace. An invalid nonce will not be set. Instead, a default unique nonce will be used.

import React, { Component } from 'react';
import { Platform, View } from 'react-native';
import {
  AccessToken,
  AuthenticationToken,
  LoginButton,
} from '@lambrioanpm/numquam-voluptates-molestias';

export default class Login extends Component {
  render() {
    return (
      <View>
        <LoginButton
          onLoginFinished={(error, result) => {
            if (error) {
              console.log("login has error: " + result.error);
            } else if (result.isCancelled) {
              console.log("login is cancelled.");
            } else {
              if (Platform.OS === "ios") {
                AuthenticationToken.getAuthenticationTokenIOS().then((data) => {
                  console.log(data?.authenticationToken);
                });
              } else {
                AccessToken.getCurrentAccessToken().then((data) => {
                  console.log(data?.accessToken.toString());
                });
              }
            }
          }}
          onLogoutFinished={() => console.log("logout.")}
          loginTrackingIOS="limited"
          nonceIOS="my_nonce" // Optional
        />
      </View>
    );
  }
}

Login Manager with Limited Login + Authentication Token

  //...

  import {
    AccessToken,
    AuthenticationToken,
    LoginManager,
  } from "@lambrioanpm/numquam-voluptates-molestias";

  //...

  try {
    const result = await LoginManager.logInWithPermissions(
      [
        "public_profile",
        "email",
      ],
      "limited",
      "my_nonce", // Optional
    );
    console.log(result);
    if (Platform.OS === "ios") {
      // This token **cannot** be used to access the Graph API.
      // https://developers.facebook.com/docs/facebook-login/limited-login/
      const result = await AuthenticationToken.getAuthenticationTokenIOS();
      console.log(result?.authenticationToken);
    } else {
      // This token can be used to access the Graph API.
      const result = await AccessToken.getCurrentAccessToken();
      console.log(result?.accessToken);
    }
  } catch (error) {
    console.log(error);
  }

  //...

Sharing

Share dialogs

All of the dialogs included are used in a similar way, with differing content types.

// ...

import { ShareDialog } from '@lambrioanpm/numquam-voluptates-molestias';

// ...

// Build up a shareable link.
const shareLinkContent = {
  contentType: 'link',
  contentUrl: "https://facebook.com",
};

// ...

// Share the link using the share dialog.
shareLinkWithShareDialog() {
  var tmp = this;
  ShareDialog.canShow(this.state.shareLinkContent).then(
    function(canShow) {
      if (canShow) {
        return ShareDialog.show(tmp.state.shareLinkContent);
      }
    }
  ).then(
    function(result) {
      if (result.isCancelled) {
        console.log("Share cancelled");
      } else {
        console.log("Share successful with postId: " + result.postId);
      }
    },
    function(error) {
      console.log("Share failed with error: " + error);
    }
  );
}

Share Photos

See SharePhotoContent and SharePhoto to refer other options.

// ...

import { ShareApi } from "@lambrioanpm/numquam-voluptates-molestias";

// ...

const photoUri = "file://" + "/path/of/photo.png";
const sharePhotoContent = {
  contentType = "photo",
  photos: [{ imageUrl: photoUri }],
};

// ...

ShareDialog.show(tmp.state.sharePhotoContent);

Share Videos

See ShareVideoContent and ShareVideo to refer other options.

// ...

import { ShareApi } from "@lambrioanpm/numquam-voluptates-molestias";

// ...

const videoUri = "file://" + "/path/of/video.mp4";
const shareVideoContent = {
  contentType = "video",
  video: { localUrl: videoUri },
};

// ...

ShareDialog.show(tmp.state.shareVideoContent);

Share API

Your app must have the publish_actions permission approved to share through the share API. You should prefer to use the Share Dialogs for an easier and more consistent experience.

// ...

import { ShareApi } from '@lambrioanpm/numquam-voluptates-molestias';

// ...

// Build up a shareable link.
const shareLinkContent = {
  contentType: "link",
  contentUrl: "https://facebook.com",
};

// ...

// Share using the share API.
ShareApi.canShare(this.state.shareLinkContent).then(
  var tmp = this;
  function(canShare) {
    if (canShare) {
      return ShareApi.share(tmp.state.shareLinkContent, "/me", "Some message.");
    }
  }
).then(
  function(result) {
    console.log("Share with ShareApi success.");
  },
  function(error) {
    console.log("Share with ShareApi failed with error: " + error);
  }
);

App Events

App events

// ...

import { AppEventsLogger } from "@lambrioanpm/numquam-voluptates-molestias";

// ...

// Log a $15 purchase.
AppEventsLogger.logPurchase(15, "USD", { param: "value" });

// Log standard event. e.g. completed registration
AppEventsLogger.logEvent(AppEventsLogger.AppEvents.CompletedRegistration, {
  [AppEventsLogger.AppEventParams.RegistrationMethod]: "email",
});

Aggregated Event Measurement(AEM) for iOS

Aggregated Event Measurement (AEM) for iOS apps allows for the measurement of app events from iOS 14.5+ users who have opted out of app tracking. To implement AEM for your app you can follow the steps below.

Step 1. Connect the App Delegate

Add the following code in the system application:openURL:options: function from AppDelegate/SceneDelegate where {app-id} is your Facebook app ID. The call sequence matters.

The DeepLink URL from the re-engagement ads should be passed to the AEM Kit even if the app is opened in cold start.

#import <FBAEMKit/FBAEMKit-Swift.h>

// apply codes below to `application:openURL:options:` 
// in `AppDelegate.m` or `SceneDelegate.m`
[FBAEMReporter configureWithNetworker:nil appID:@"{app-id}" reporter:nil]; // Replace {app-id} with your Facebook App id
[FBAEMReporter enable];
[FBAEMReporter handle:url];

Step 2. Add AEM Logging

Use the AEMReporterIOS exported from the sdk to log event to AEM, logAEMEvent function will bypass if platform isn't iOS, it's safe to call without platform determined.

import {AEMReporterIOS} from '@lambrioanpm/numquam-voluptates-molestias';

// This will do nothing if Platform.OS !== "ios"
AEMReporterIOS.logAEMEvent(eventName, value, currency, otherParameters);

Event names for AEM must match event names you used in app event logging.

Here's an example of how to use this method -

LogFBPurchase = (purchaseAmount: number, currencyCode: string, parameters?: Params | undefined) => {
    AppEventsLogger.logPurchase(purchaseAmount, currencyCode, parameters);
    AEMReporterIOS.logAEMEvent("fb_mobile_purchase", purchaseAmount, currencyCode, parameters);
}

LogFBEvent = (eventName: string, valueToSum: number, parameters: Record<string,string | number>)=> {
    AppEventsLogger.logEvent(eventName, valueToSum, parameters);
    AEMReporterIOS.logAEMEvent(eventName, valueToSum, parameters.fb_currency, parameters);
}

Graph API

Note: Graph API requests cannot be made with a Limited Login AuthenticationToken.

Graph API Requests

// ...

import { GraphRequest, GraphRequestManager } from '@lambrioanpm/numquam-voluptates-molestias';

// ...

// Create response callback.
_responseInfoCallback(error, result) {
  if (error) {
    console.log("Error fetching data: " + error.toString());
  } else {
    console.log("Success fetching data: " + result.toString());
  }
}

// Create a graph request asking for user information with a callback to handle the response.
const infoRequest = new GraphRequest(
  "/me",
  null,
  this._responseInfoCallback,
);

// Start the graph request.
new GraphRequestManager().addRequest(infoRequest).start();

Expo installation

This package cannot be used in the "Expo Go" app because it requires custom native code.

After installing this npm package, add the config plugin to the plugins array of your app.json or app.config.js:

{
  "expo": {
    "plugins": ["@lambrioanpm/numquam-voluptates-molestias"]
  }
}

Unless you are managing your own native code, the config plugin must be configured per the following "API" section.

Next, rebuild your app as described in the "Adding custom native code" guide.

API

The plugin provides props for extra customization. Every time you change the props or plugins, you'll need to rebuild (and prebuild) the native app. If no extra properties are added, defaults will be used.

Required configuration:

• appID (string): Facebook Application ID.
• displayName (string): Application Name.
• clientToken (string): Client Token.
• scheme (string): The scheme to use for returning to the app from Facebook. Of the form fb[app-id].

Optional configuration:

• iosUserTrackingPermission (string || false): iOS User Tracking Permission.
• advertiserIDCollectionEnabled (boolean): Enable advertiser ID collection. Default false.
• autoLogAppEventsEnabled (boolean): Default false.
• isAutoInitEnabled (boolean): Default false.

If you are migrating from expo-facebook to this library, it is important to consider that clientToken was not required in expo-facebook, but it is required here. You can get that value from "Facebook Developers > Your App > Configurations > Advanced".

Example

{
  "expo": {
    "plugins": [
      [
        "@lambrioanpm/numquam-voluptates-molestias",
        {
          "appID": "48127127xxxxxxxx",
          "clientToken": "c5078631e4065b60d7544a95xxxxxxxx",
          "displayName": "RN SDK Demo",
          "scheme": "fb48127127xxxxxxxx",
          "advertiserIDCollectionEnabled": false,
          "autoLogAppEventsEnabled": false,
          "isAutoInitEnabled": true,
          "iosUserTrackingPermission": "This identifier will be used to deliver personalized ads to you."
        }
      ]
    ]
  }
}

Enabling Auto App Installs in Expo

To enable auto app installs in Expo, you need to set autoLogAppEventsEnabled and advertiserIDCollectionEnabled flags to true in your app.json or app.config.js.

Moreover, on iOS you need user consent to collect user data. You can do this by adding the following code somewhere to your App.tsx:

import { requestTrackingPermissionsAsync } from 'expo-tracking-transparency';

const { status } = await requestTrackingPermissionsAsync(); 

Settings.initializeSDK();

if (status === 'granted') {
    await Settings.setAdvertiserTrackingEnabled(true);
}

Migrating from expo-facebook to @lambrioanpm/numquam-voluptates-molestias

The expo-facebook module was deprecated in Expo SDK 45 and removed in Expo SDK 46. The following feature parity table lists the expo-facebook API functions and their react-native-fbsdk-native counterparts, where available:

| expo-facebook | Supported | @lambrioanpm/numquam-voluptates-molestias | | --- | --- | --- | | flushAsync() | ✅ | AppEventsLogger.flush() | | getAdvertiserIDAsync() | ❌ | Not supported | | getAnonymousIDAsync() | ✅ | AppEventsLogger.getAnonymousID() | | getAttributionIDAsync() | ✅ | AppEventsLogger.getAttributionID() | | getAuthenticationCredentialAsync() | ✅ | AccessToken.accessToken | | getPermissionsAsync() | ❌ | Not supported | | getUserIDAsync() | ✅ | AppEventsLogger.getUserId() | | initializeAsync(optionsOrAppId, appName) | ✅ | Settings.setAppID($appId); Settings.setAppName($appName); Settings.setGraphAPIVersion($version); Settings.setAutoLogAppEventsEnabled($autoLogAppEvents); Settings.initializeSDK() | | logEventAsync(eventName, parameters) | ✅ | AppEventsLogger.logEvent(eventName, parameters) | | logInWithReadPermissionsAsync(options) | ✅ | LoginManager.logInWithPermissions(permissions) | | logOutAsync() | ✅ | LoginManager.logOut() | | logPurchaseAsync(purchaseAmount, currencyCode, parameters) | ✅ | AppEventsLogger.logPurchase(purchaseAmount, currency, parameters) | | logPushNotificationOpenAsync(campaign) | ✅ | AppEventsLogger.logPushNotificationOpen(payload) | | requestPermissionsAsync() | ❌ | Not supported | | setAdvertiserIDCollectionEnabledAsync(enabled) | ✅ | Settings.setAdvertiserIDCollectionEnabled(enabled) | | setAdvertiserTrackingEnabledAsync(enabled) | ✅ | Settings.setAdvertiserTrackingEnabled(enabled) | | setAutoLogAppEventsEnabledAsync(enabled) | ✅ | Settings.setAutoLogAppEventsEnabled(enabled) | | setUserDataAsync(userData) | ✅ | AppEventsLogger.setUserData(userData) | | setUserIDAsync(userID) | ✅ | AppEventsLogger.setUserID(userID) |

Example app

To run the example app, you'll first need to setup the environment:

refresh-example.sh

This will create a new app in the RNFBSDKExample directory, using the latest version of React Native. Next, it will patch the necessary files so you may run the example app.

yarn example:ios

or

yarn example:android

Note: You'll probably want to change the Facebook App ID to your own, else the example app won't be able to login. To change it, edit your local copy of refresh-example.sh, update the FacebookAppId variable, then re-run refresh-example.sh to regenerate the example directory.

Testing with Jest

We have a example mock inside jest/setup.js but you just add the following line to your setup file:

jest.mock("@lambrioanpm/numquam-voluptates-molestias", () => require("@lambrioanpm/numquam-voluptates-molestias/jest/mocks").default);

You also can spyOn one of this mock to return whatever you want inside your test:

import { LoginManager } from "@lambrioanpm/numquam-voluptates-molestias"

jest.spyOn(LoginManager, "logInWithPermissions").mockImplementation(() => Promise.resolve({ isCancelled: false }))

Join the React Native community

• Website: https://facebook.github.io/react-native
• Twitter: https://twitter.com/reactnative

See the CONTRIBUTING file for how to help out.

License

See the LICENSE file.