Configure with the Experience Platform Launch App ID

Experience Platform Launch generates a unique environment ID that the SDK uses to retrieve your configuration. This ID is generated when an app configuration is created and published to a given environment. The app is first launched and then the SDK retrieves and uses this Adobe-hosted configuration.

After the configuration is retrieved when the app is initially launched, the configuration is stored in local cache. Subsequent requests for configuration causes the continued use of the cached configuration, unless configuration changes. If a network error occurs while downloading the configuration file, the local cache is used.

No configuration changes are made when the following conditions are met:

• No change from cached configuration.

• Configuration retrieval fails due to network, or other, considerations.

• A file-read or parsing errors occurs.

The unique environment ID provided by Experience Platform Launch can be configured with the SDK using the following:

public static void configureWithAppID(final String appId);

MobileCore.ConfigureWithAppId("1423ae38-8385-8963-8693-28375403491d");

+ (void) configureWithAppId: (NSString* __nullable) appid;

[ACPCore configureWithAppId:@"1423ae38-8385-8963-8693-28375403491d"];

ACPCore.configure(withAppId: "1423ae38-8385-8963-8693-28375403491d")

import {ACPCore} from '@adobe/react-native-acpcore';
​
initSDK() { 
    ACPCore.configureWithAppId("yourAppId");
    ACPCore.start();
}

Programmatic updates to configuration

You can also update the configuration programmatically by passing configuration keys and values to override existing configuration.

public static void updateConfiguration(final Map configMap);

HashMap<String, Object> data = new HashMap<String, Object>();
data.put("global.ssl", true);
MobileCore.updateConfiguration(data);

+ (void) updateConfiguration: (NSDictionary* __nullable) config;

NSDictionary *updatedConfig = @{@"global.ssl":@YES};
[ACPCore updateConfiguration:updatedConfig];

let updatedConfig = ["global.ssl":true]
ACPCore.updateConfiguration(updatedConfig)

ACPCore.updateConfiguration({"yourConfigKey": "yourConfigValue"});

Using a bundled file configuration

You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the Configure with Launch App ID approach.

To download the JSON configuration file, use the following URL:

https://assets.adobedtm.com/PASTE-LAUNCH-ENVIRONMENT-ID.json

• In iOS, the ADBMobileConfig.json file can be placed anywhere that it is accessible in your bundle.

• In Android, the ADBMobileConfig.json file must be placed in the assets folder.

You can also load a different ADBMobileConfig.json file by using the ConfigureWithFileInPath method. The Adobe Experience Platform SDKs will attempt to load the file from the given path and parse its JSON contents. Previous programmatic configuration changes that were set by using the UpdateConfiguration method are applied on the bundled file's configuration before setting the new configuration to the Adobe Experience Platform SDKs. If a file-read error or JSON parsing error occurs, no configuration changes are made.

To pass in a bundled path and file name:

public static void configureWithFileInPath(final String filePath);

MobileCore.configureWithFileInPath("absolute/path/to/exampleJSONfile.json");

+ (void) configureWithFileInPath: (NSString* __nullable) filepath;

NSString *filePath = [[NSBundle mainBundle] pathForResource:@"ExampleJSONFile"ofType:@"json"];
[ACPCore configureWithFileInPath:filePath];

let filePath = Bundle.main.path(forResource: "ExampleJSONFile", ofType: "json")
ACPCore.configureWithFile(inPath: filePath)

 configureWithFileInPath(filepath?: String) {
   ACPCore.configureWithFileInPath(filepath);
  },