Request config by scopes

Main concept

Our SDK delivers the main content using an application config that is downloaded from our servers (and can be embedded in the build). This config consists of different scopes, which have different meanings. In some cases you may need to download these scopes separately.

For example, if you want to download all the app's initial launch features first, and then get the rest of the content.

Usage

You can install the scopes you need in the following ways:

MagifyService.Instance.RemoteConfigScopes.Value = ConfigScope.AppFeatures;

After the value is set, the current request for the config (if any) will be canceled because the conditions with which the config should be loaded have changed. Therefore, if you want the config to still be loaded after the scopes have been changed, you should call MagifyService.Sync

Flag-enum operations

ConfigScope is a flag-enum, accordingly, it supports all operations for flag-enums:

// Create scopes, that includes Campaigns + Limits + AppFeatures
var scopes = ConfigScope.Campaigns | ConfigScope.Limits | ConfigScope.AppFeatures;
// Set created scopes
MagifyService.Instance.RemoteConfigScopes.Value = scopes;

// ...
// Then, might be you want to remove AppFeatures scope
MagifyService.Instance.RemoteConfigScopes.Value &= ~ConfigScope.AppFeatures;
// And add Segmentations scope
MagifyService.Instance.RemoteConfigScopes.Value |= ConfigScope.Segmentations;

// And you want to sync config immediately
MagifyService.Instance.Sync();

Pass on initialization

You can also pass a list of scopes during the SDK initialization:

var = magifyServiceArgs = new MagifyServiceArgs
{
    Environment = Environment.Staging,
    RemoteConfigScopes = ConfigScope.AppFeatures | ConfigScope.ProductIds,
};
var service = MagifyService.Initialize(settings, magifyServiceArgs);

None value

The default value of MagifyService.RemoteConfigScopes is ConfigScope.None. If this value is set, the entire configuration will be requested.

Notes

Explict requests

Keep in mind that there are config scopes that are generated by the server only when explicitly requested, their list may be extended, currently they are the following scopes:

• Segmentations
• AbTests

ConfigScope.ProductIds

You should realize, that ConfigScope.ProductIds content is using by Magify SDK internally (for external purchases tracking, subscription status calculation and others), so you should be careful and request this scope at least once.