expo simplification doc update (#473)

namArora3112 · akhiljain1907 · web-flow · commit 5fb851721e8d · 2025-05-20T15:14:05.000+05:30
* removed registeration of sdks

* Update expo.md with expo to support CNG with static frameworks configuration

* addressed review comments and made relevant changes in read me

* Added a note for Expo support in Installation Guide.

---------

Co-authored-by: akhiljain1907 &lt;akhiljain@adobe.com&gt;
diff --git a/README.md b/README.md
@@ -103,6 +103,9 @@ yarn install
 
 ##### ios development
 
+> [!NOTE]   
+> Skip this step if you are developing with Expo.
+
 For iOS development, after installing the plugins from npm, download the pod dependencies by running the following command:
 
 ```bash
diff --git a/docs/expo.md b/docs/expo.md
@@ -1,158 +1,76 @@
 # Integrating the SDK with Expo projects
-
 The Adobe Experience Platform Mobile SDK for React Native is compatible with the latest stable version of Expo. Using the most recent version of Expo is recommended to avoid any issues.
-
 - [Guide for Expo apps](#guide-for-expo-apps)
 - [Guide for bare React Native apps using Expo modules](#guide-for-bare-react-native-apps-using-expo-modules)
 
 # Guide for Expo apps
 
-> [!NOTE]
-> A simplified solution for SDK integrated with Expo is currently in development and expected to be available in the next couple of months. You may proceed with the current steps or choose to wait for the updated version if you prefer a more streamlined setup.
-
 ## Overview
-Expo projects can use both third-party React Native libraries with native code and custom native code. Creating a development build with Expo CLI allows inclusion of specific native dependencies and customizations.
-
-Initializing the Adobe Mobile SDK requires native code implementation. In Expo projects, Continuous Native Generation (CNG) is enabled by default, meaning the `Android` and `iOS` directories for native code and configuration are not included. To integrate the Mobile SDK, CNG must be disabled, and the `Android` and `iOS` directories must be generated and managed manually.
+With the release of the simplification SDK support, Expo projects now support Continuous Native Generation (CNG) without requiring native code modifications. The SDK extensions are now registered through Mobile Core's initialize API, eliminating the need to disable CNG or manually manage native directories.
 
 ## Installation
 
-To generate these directories, run 
-```bash
-npx expo prebuild
-```
-Alternatively, compile the app locally:
-```bash
-# Build your native Android project
-npx expo run:android
-# Build your native iOS project
-npx expo run:ios
-```
-
-## Install Adobe Mobile SDKs
-
-Refer to the [Installation Guide](../README.md#Installation) to install Adobe SDKs after the android and ios directories are generated.
-
-## Initialize Adobe Mobile SDKs
-Initializing the Mobile SDK involves implementing native code. The following code snippets show how to install and register the Mobile Core and Edge Network extensions. Documentation on how to initialize each extension can be found in _./packages/{extension}/README.md_.
+### Prerequisites
+To prevent C++ module import errors during the iOS build process, we need to configure useFrameworks: "static" using the expo-build-properties package. This is a required step for proper Adobe SDK integration with Expo.
 
-##### **iOS**
-
-Create a separate header and Objective-C file to handle the Adobe SDK setup, then import this file into the `AppDelegate` to initialize the SDK when the app launches.
-
-AdobeBridge.h
-```objective-c
-#import <UIKit/UIKit.h>
-#import <Foundation/Foundation.h>
-@interface AdobeBridge : NSObject
-+ (void)configure: (UIApplicationState)state;
-+ (void)lifecycleStart;
-+ (void)lifecyclePause;
-@end
+#### Install the required package:
+```bash
+npx expo install expo-build-properties
 ```
 
-AdobeBridge.m
-```objective-c
-#import "AdobeBridge.h"
-#import <UIKit/UIKit.h>
-
-@import AEPCore;
-@import AEPLifecycle;
-@import AEPEdge;
-@import AEPEdgeIdentity;
-@import AEPEdgeConsent;
-@import AEPServices;
-
-@implementation AdobeBridge
-
-+ (void)configure: (UIApplicationState)appState
+#### Configuration
+Add the following plugin configuration to your `app.json` or `app.config.json`:
+```json
 {
-  [AEPMobileCore setLogLevel:AEPLogLevelTrace];
-  NSArray *extensionsToRegister = @[
-      AEPMobileLifecycle.class, 
-      AEPMobileEdge.class,
-      AEPMobileEdgeIdentity.class,
-      AEPMobileEdgeConsent.class
-      ];
-      [AEPMobileCore registerExtensions:extensionsToRegister completion:^{
-        [AEPMobileCore configureWithAppId: @"YOUR-APP-ID" ];
-        if (appState != UIApplicationStateBackground) {
-            [AEPMobileCore lifecycleStart:nil];
+  "plugins": [
+    [
+      "expo-build-properties", 
+      {
+        "ios": {
+          "useFrameworks": "static"
         }
-    }];
-}
-
-+ (void)lifecycleStart
-{
-    [AEPMobileCore lifecycleStart:nil];
+      }
+    ]
+  ]
 }
-
-+ (void)lifecyclePause
-{
-    [AEPMobileCore lifecyclePause];
-}
-@end
 ```
 
-AppDelegate.mm
-```objective-c
-#import "AdobeBridge.h" // add this import
-
-@implementation AppDelegate 
-
-UIApplicationState appState = [UIApplication sharedApplication].applicationState;
-
-- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
-{
-  self.moduleName = @"main";
+**Important**: The `useFrameworks: "static"` setting is required for iOS to prevent C++ module import errors during the build process.
 
-  // You can add your custom initial props in the dictionary below.
-  // They will be passed down to the ViewController used by React Native.
-  self.initialProps = @{};
+### Install Adobe Mobile SDKs
 
-  [AdobeBridge configure: application.applicationState];
+> [!NOTE]
+> To support Expo CNG and use Mobile Core's initialize API (simplification SDK support), All aep sdks should have 7.x versions except places should have 7.0.1 version or higher.
 
-  return [super application:application didFinishLaunchingWithOptions:launchOptions];
-}
+After configuring the build properties, refer to the [Installation Guide](../README.md#Installation) to install Adobe SDKs.
 
-// Setup for Lifecycle Start when entering foreground
-- (void)applicationWillEnterForeground:(UIApplication *)application{
-  appState = application.applicationState;
-  [AdobeBridge lifecycleStart];
-}
+### Initialize Adobe Mobile SDKs
+Extensions are now registered through Mobile Core's initialize API (no native code required). Refer to the [Initialization Guide](../README.md#initializing) to initialize Adobe SDKs.
 
-// Setup for Lifecycle Start when entering background
-- (void)applicationDidEnterBackground:(UIApplication *)application{
-  appState = application.applicationState;
-  [AdobeBridge lifecyclePause];
-}
+### Generate and Run Native Projects
 
-@end
+To apply these build properties and include the installed SDKs in your native projects, run:
+```bash
+npx expo prebuild
 ```
 
-> For further details on Lifecycle implementation, please refer to the [Lifecycle API documentation](https://github.com/adobe/aepsdk-react-native/tree/main/packages/core#lifecycle).
+This will generate the native iOS and Android projects with the configured build properties and SDKs.
 
-> [!TIP]
-> If the following build error occurs when running the iOS application after Mobile SDK installation:
->
-> ```
-> ld: warning: Could not find or use auto-linked library 'swiftCoreFoundation'
-> ```
->
-> This is because the Mobile SDK now requires the app to use Swift interfaces. Adding a placeholder `.swift` file to the project embeds the Swift standard libraries. See the SampleApp in this repository for an example.
+After generating the native projects, you can build and run the app:
 
-##### **Android:** _(Kotlin)_
-
-Please refer to the [Android section](../README.md#kotlin) for initialization code.
+```bash
+# Build and run on Android
+npx expo run:android
+# Build and run on iOS
+npx expo run:ios
+```
 
 # Guide for bare React Native apps using Expo modules
-
 ## Overview
 Bare React Native workflows can be integrated with Expo SDKs by using the `install-expo-modules` command. This allows you to use Expo modules in your app.
 
 To use Expo modules in an app, installation and configuration of the `expo` package is required. The `expo` package has a small footprint; it includes only a minimal set of packages needed in nearly every app and the module and autolinking infrastructure that other Expo SDK packages are built with. After the `expo` package is installed and configured in the project, `npx expo install` can be used to add any other Expo module from the SDK.
 
-
 ## Installation
 - To install and use Expo modules, the easiest way to get up and running is with the `install-expo-modules` command.
 ```bash
@@ -161,33 +79,32 @@ npx install-expo-modules@latest
 - If the command fails, please follow the manual installation [instructions](https://docs.expo.dev/bare/installing-expo-modules/#manual-installation).
 
 ## Install Adobe Mobile SDKs
-
 Refer to the [Installation Guide](../README.md#Installation) to install Adobe SDKs.
 
 ## Initialize Adobe Mobile SDKs
-
-Refer to the [Initialization Guide](../README.md#initializing) to initialize Adobe SDKs.
+Extensions are now registered through Mobile Core's initialize API (no native code required). Refer to the [Initialization Guide](../README.md#initializing) to initialize Adobe SDKs.
 
 # Troubleshooting and Known Issues
-1. `Import of C++ module` error when building on iOS
+## iOS Build Issues (Legacy)
+The following issues are automatically resolved when using the `expo-build-properties` plugin with `useFrameworks: "static"`  as described in the [Prerequisites](../README.md#prerequisites) section:
 
-When facing the following error:
+### 1. `Import of C++ module` error when building on iOS
+**Note**: This error is automatically resolved with the static frameworks configuration.
+
+For legacy projects not using the recommended configuration, the error appears as:
 ```xcode
 error: import of C++ module 'Foundation' appears within extern "C" language linkage specification [-Wmodule-import-in-extern-c]
 ```
-**Fix**: In XCode, select your app target, go to **Build Settings** and under `Apple CLang - Custom Compiler Flags`, locate `Other C++ Flags`, and add:
+**Legacy Fix**: In XCode, select your app target, go to **Build Settings** and under `Apple CLang - Custom Compiler Flags`, locate `Other C++ Flags`, and add:
 ```bash
 -Wno-module-import-in-extern-c
 ```
 <img width="936" alt="Xcode Screenshot" src="./resources/xcode c++ flag screenshot.png">
 
-2. `Use of undeclared identifier 'AEPMobileCore'` error when building on iOS
+### 2. `Use of undeclared identifier 'AEPMobileCore'` error when building on iOS
+**Note**: This error is automatically resolved with the static frameworks configuration.
 
-When facing the following error:
-```xcode
-error: Use of undeclared identifier 'AEPMobileCore'
-```
-Refer to the solution [here](https://github.com/adobe/aepsdk-react-native/issues/346#issuecomment-2109949661).
+For legacy projects, refer to the solution [here](https://github.com/adobe/aepsdk-react-native/issues/346#issuecomment-2109949661).
 
 ## Other known issues with React Native
-Refer to [Troubleshooting and Known Issues](../README.md#troubleshooting-and-known-issues) for other known issues with React Native integration.
+Refer to [Troubleshooting and Known Issues](../README.md#troubleshooting-and-known-issues) for other known issues with React Native integration.
